interfaces of these components. SOA is typically useful when you are crossing heterogeneous technical boundaries, organizations, domain etc. In .NET SOA technically uses Web services to communicate with each service which is crossing boundaries. You can look SOA which sits on top of web services and provides a workflow. SOA uses service components which operate in their own domain boundary. Let us note some points of service :-
268
√
They are independent components and operate in their own boundary and own technology.
√
They have well defined interfaces which use XML and WSDL to describe themselves.
√
Services have URL where anyone can find them and clients can bind to these URL to avail for the service.
√
Services have very loosely coupled architecture. In order to communicate to service you only have to know the WSDL. Your client can then generate proxy from the WSDL of the service.