|
|
|
|
|
Service Oriented Architecture |
|
|
|
A service-oriented architecture is essentially a collection of services. These
services communicate with each other. The communication can involve either
simple data passing or it could involve two or more services coordinating some
activity. A means of connecting services to each other is also needed. Service
oriented architectures are not a new thing. The first service oriented
architecture for many people in the past was with the use DCOM or Object
Request Brokers (ORBs) based on the CORBA specification.
|
|
|
|
Services |
A service is a function that is well-defined, self-contained, and does not
depend on the context or state of other services. |
 |
|
|
|
|
Connections |
Web services are the most likely connection technology of service oriented
architectures. Web services essentially use a technology called XML (thru SOAP
specifications) to create a connection. The figure at right illustrates a basic
service oriented architecture. It shows service consumers (client tier on the
left) and service providers (web services in the middle tier). The
service providers (web services) return a response message to the client tier
(on the left). The request and subsequent response connections are defined in
some way that are understandable to both the service consumers and service
providers. These connections are defined through a standard web service
technology called SOAP.
Examples of services could include the following:
-
Login
-
Logoff
-
GetCustomers
-
GetOrders
-
etc.
Based on the example list above, you can see that these services could be
utilized in various "mix and match" scenarios to create a solution. If
architected correctly, these services can have a high degree of reusability for
use with multiple different types of web application solutions.
|
|
|
|
|
|
Software Experts .NET develops all new web application solutions
utilizing a service oriented architecture. |
|
|
|
|