According to Wikipedia, Service Oriented Architecture (SOA) is a software architecture where functionality is grouped around business processes and packages as interoperable services. But search the web and you are probably going to find a number of different definitions and implementations. Dr. Jim Webber, the Global Architecture lead for ThoughtWorks and co-author of the book "Developing Enterprise Web Services - An Architect's Guide", explains this in and an interview on the .Net Rocks Internet radio show (listen here).
I personally have seen SOA implementations that were geared to .Net applications as consumers because the messages were DataSets which although serialize nicely, may be a problem for a Java application to understand. One of the tenets of SOA (the way I understand it) is supposed to be interoperability: platform, language and protocol agnostic. Otherwise you just have a bunch of web services. So are those implementations REALLY SOA?
No comments:
Post a Comment