none
When to use SOA vs. simpler client-server RRS feed

  • Question

  • The Service-Oriented Integration Prescriptive Architecture pattern described at http://msdn2.microsoft.com/en-us/library/ms978594.aspx documents the key liability of using Service-Oriented Integration as "the performance cost of serializing, deserializing, and parsing XML documents" as well as the larger size of XML documents.

    I would suggest a further liability: implementing far more than what the client actually needs. If you use SOA when a simple client-server arrangement will meet the need, you wind up with complexity that impedes further enhancements.

    Would you recommend designing every system that uses web services with a Service Oriented Architecture? How do you decide?

    Sunday, January 28, 2007 4:22 AM

Answers

  • If you are interested in finding alternatives to the web service stack then you should take a look at the REST paradigm:

    http://en.wikipedia.org/wiki/REST

    http://www.petefreitag.com/item/431.cfm

    Personally I prefer the use of web services and SOAP - I believe they lead to few support issues from a techincal skills perspective in the long term, most developers have heard if not used web services, how many people will know anything about a bespoke RESTful system outside of the original develpoment team.

     

     

     

    Sunday, January 28, 2007 7:25 PM