title

Service Oriented Architecture Compass

Content-Type

text/html; charset=UTF-8

viewport

width = device-width

description

There are a lot of different definitions of SOA floating about, but when you strip away all the suit-mumble, it's concepts every Unix person understands intimately: loose coupling, reuse and interoperability. The distinction between SOA and an API is a little fuzzy at the edges, but an example might clear that up: suppose you have something that can be queried to return customer contact information. In a traditional API, that's going to give you back a structured record and if something new is added to that record (like a new 'PDA ip address' field), the API probably has to change along with the clients that use it. With a SOA implementation, the data is probably returned in XML, and a client happily ignores fields it doesn't need or understand. This decoupling is what makes SOA more powerful, but note that it doesn't necessarily have anything to do with XML; any web service like chargen, daytime etc. is a primitive example of a service priented application.

author

Anthony Lawrence

alternate

https://feeds2.feedburner.com/aplawrence/ZPYH

alternate

https://feeds2.feedburner.com/SiteNewsForAplawrenceUnixLinuxAndMacOsXResources

alternate

https://feeds2.feedburner.com/aplawrence/DOLL

alternate

https://feeds2.feedburner.com/aplawrence/DrTi

alternate

https://feeds2.feedburner.com/Web-htmlRssSiteNewsForAplawrencecom