This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: SOA does not simplify communication?
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
"Services should be objects with lots of methods and represent effectively a whole application."
Umm, no. Consider a more "document-centric" approach. The only kind of object I could consider comparing a service to would be the Active Object Pattern, and that falls horribly short.
"SOA seems to be fundamentially about a message bus."
Well, if that's what it seems to you, I can't argue the point. But, if we take the "seems" out of the equation, it would be much more accurate to say that an effective SOA implementation might use a message bus of some kind.
"...SOA has no equvalent concept. Instead, it concentrates on the transfer of arbitrary messages belonging to arbitrary protocols. It promotes the idea that object-orientation and RPC with their arbitrary methods on arbitrary objects with arbitrary parmeter lists are a suitable means of addressing the communications issue."
No, it does NOT "[promote] the idea that object-orientation and RPC with their arbitrary methods on arbitrary objects with arbitrary parmeter lists are a suitable means of addressing the communications issue". Exactly the opposite.
Sorry, Benjamin, but I think that proving REST is "better" than SOA by distorting the main principles of SOA isn't helping. If you like REST, use it. The grass may not be greener on the other side, but let each tend to their own garden.
Previous Topic
