Introduction
For many organizations, the logical starting place for investigating service-oriented architecture is the consideration of Web services. However Web services are not inherently service oriented. A Web service merely exposes a capability that conforms to Web services protocols.
It is an attempt to develop yet another means for software module integration. Rather than defining an API, SOA defines the interface in terms of protocols and functionality. An endpoint is the entry point to such an SOA implementation.
Service-orientation requires loose coupling of services with operating systems, and other technologies that underlie applications. SOA separates functions into distinct units, or services[1], which developers make accessible over a network in order that users can combine and reuse them in the production of applications.
We have progressed from modules, to objects, to components, and now to services. However in many respects the naming of SOA is unfortunate. Whilst SOA is of course about architecture, it is impossible to constrain the discussion to architecture, because matters such as business design and the delivery process are also important considerations. A more useful nomenclature might be Service Orientation (or SO). There are actually a number of parallels with object orientation (or OO) and component-based development (CBD):
Service-oriented architectures are not a new thing. The first service-oriented architecture for many people in the past was with the use DCOM.
Note:These are few points i have which i posted while i was browsing on this Topic.
For More details visit:
http://msdn.microsoft.com/en-us/library/aa480021.aspx
http://www.service-architecture.com/web-services/articles/service-oriented_architecture_soa_definition.html.
No comments:
Post a Comment