"We didn't start the fire ... it was always burning since the world's been turning ..." [Billy Joel 1989]. Is SOA the "Same Old Architecture?" or is it "Simply Over Ambitious?" Let's apply SOA's arsenal:: XML, BPM, Services, SOAP, Web Services - to the real world and find out. Let's put out some fires.

« The word 'enterprise'' - industry’s confusion, a blogger’s bliss | Main | Hype seems to be over, reality sinking in...!! »

SOA is not the same as Web services

SOA and Web services are not the same

 

The industry has witnessed enough hype on SOA. A common source of confusion in architects mind is whether Web services are same as SOA?

 

While web services have evolved as a technology for distributed computing based on standardization of different imperatives involved in inter application communications (e.g. standard

for data, standard for messages being exchanged, standard for describing of the application functionality etc.). Thus Web services based on these core set of standards including XML Schema, SOAP, WSDL are merely yet another mechanism for distributed applications to communicate. It is vital to understand this.

 

SOA on the other hand is an architectural paradigm which is based on a set of principles for any software functionality provider to interact with potential users of the software. In particular SOA principles advocate a loosely coupled mechanism for software providers to interact with other requestors via a strict contract which is indendepent of the requestor. Given this kind of goal of SOA, a key question is whether SOA is realizable only by Web services?

 

Key thing to understand is Web services do bring a high level of standardization and the interoperability thereupon to enable different providers to interact, however it is not necessary to use Web services to achieve SOA always. e.g. in a pure J2EE environment a Web service would be an overkill.

 

Likewise it is possible to use Web services not necessarily in a SOA based design, by using tight coupling as in RPC kind of invocations. Hence it is possible to do Web services without SOA principles.

-

 

TrackBack

TrackBack URL for this entry:
http://www.infosysblogs.com/soa-mt/mt-tb.fcgi/11

Comments

It is good Artcile clarifying many doubts

I completely agree with last lines. As you have pointed out that there are certain differences (potential advantages) in architectures while using web services.

WS boosts of using document style messaging to allow asynchronous communication. Also, it can be made event-driven using ws-notifications.

WS also helps exposing legacy applications as services, hence enabling reusability.

Just a question : How is all these standards coming in web services be managed and merged? Are we heading towards some fixed and complete standards, or is it divulging now? Hope it is pondered in your next blogs...

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)