SOA

[Scott M.]

As I begin to really look into SOA and get it straight in my mind that SOI
doesn't mean SOA, I've begun thinking about a simple example and am
wondering how it might be best set up as an SOA.

Can those, in the know, comment on the following scenario:

Let's take a simple scenario where a user needs to login to a system so that
they can view details about their account.

Which would make more sense (if any) to set this up as an SOA:

1a. Create a service that performs the login against a database and returns
a sort of login id that is used to indicate that the user is logged in.
1b. Create a service to accept a log in id and an account number to verify
the log in, perform the account lookup and return the account information.
1c. Create a service to perform a logout operation.

2a. Create a service that accepts login credentials and an account number,
does the login, looks up the account and returns the data and performs the
logout.

What I'm struggling with here is trying to envision how granularity and
security might be designed correctly for SOA.

I realize that this is a simple, incomplete example and that there is no one
correct way to design SOA, but I'm just trying to get on the right track
here.

Thanks!

 

[Steven Cheng]

Hi Scott,

As for SOA, it is a new concept and there is no actual component or service
called SOA(which you can create or use). You can use SOA principles and
concepts to develop your system/applications. In .NET 3.0 the WCF provide
you the fundemental for building some SOA like application(service based).
You can look for more info in the SOA center:

#Service Oriented Architecture
http://msdn2.microsoft.com/en-us/architecture/aa948857.aspx

http://searchwindevelopment.techtarget.com/news/article/0,289142,sid8_gci122
5691,00.html

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead



==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.



Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------

 

[Scott M.]

Hi Steven,

I'm aware that SOA isnt' a component and is an architectural paradigm. I've
also purchased some good reading material on it, but am just beginning with
it.

That's why I was hoping to get some comments about the simple scenario I've
proposed below.

Thanks,

Scott

 

[Steven Cheng]

Thanks for your reply Scott,

Basically, you can try implementing all those fundamental functionality in
your system/application as service, you can consider using the WCF in .NET
3.0 to build such services layer. Also, it is hard to say what granularity
is best since it may depend on your actual scenario to determine the
granularity of the services you'll implement.

As for the detailed case (login service), I think all those options is
doable as long as you put those login functions in the same service. For
security granularity, would you provide more about what you care about on
the security?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------

Reply-To: "Scott M." <[email protected]>
From: "Scott M." <[email protected]>
References: <#[email protected]>

 

[Scott M.]

Hi Steven,

My question, for right now, is not about implemenation technologies, so I'm
not too concerned about using WCF, Remoting or Web Services. I'm just
trying to get a feel for the difference between service oriented
implementation vs. service oriented architecture.

I'm trying to get a feel for whether scenario #1 or #2 best fits with SOA as
opposed to SOI.

Based on your reply, I think you are saying that scenario #1 would NOT be a
good way of designing this as a SOA as it details multiple services that
have to work together in order to accomplish the task and cannot be used
independently, whereas scenario #2 is more of a complete and encapsulated
service. Would that be an accurate way of describing what you are saying?

Thanks,

Scott

 

[Steven Cheng]

Thanks for your reply Scott,

I'm not totally saying that #1 is not good. As I mentioned, it just depend
on the granularity of your actual service. My opinion is that those
operations that are similar to eachother can be grouped in the same service
together rather than build a separate one for every operation. Maybe that's
just an simple example you raise and in your case the operations would be
much more complex. Anyway, just try keep each service at the proper size
(contains enough operations) so that they can be reused as much as possible
and convenient to update later.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------

 

[Scott M.]

Thanks Steven.

Thanks for your reply Scott,

I'm not totally saying that #1 is not good. As I mentioned, it just depend
on the granularity of your actual service. My opinion is that those
operations that are similar to eachother can be grouped in the same
service
together rather than build a separate one for every operation. Maybe
that's
just an simple example you raise and in your case the operations would be
much more complex. Anyway, just try keep each service at the proper size
(contains enough operations) so that they can be reused as much as
possible
and convenient to update later.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no
rights.