protocol7 home

SOA == WS?

My colleague Mårten just replied to Jimmy Nilssons question regarding whether SOA == WS. As Mårten, I think that equation is not necessarily true, possibly not even desirable.

I view services as a well designed (from both a business and technical standpoint) interface to perform a function. This is not bound to a particular technology (such as WS-*).  In fact, I think the whole WS-* mess in many cases is holding back the possibilities of building a working SOA due to its complexity. I’m certainly a part of the Loyal WS-Opposition and prefer to use the strengths of each protocol rather than adding a leaky layer on top. In my world, using HTTP (preferably REST like) and a MOM (like ActiveMQ or WebSphere MQ) will suffice for building a very strong and flexible backbone to enable SOA.

But, the hard part of building a SOA is not the technical details (that’s been solved for years), it’s finding a appropriate services based on the business requirements. The experience in this area is far less advanced.

Tags: . 1 Comment »

One Response

  1. marten.gustafson » SOA - More process than technology(?) Says:
    [...] As Niklas points out in his reply/follow-up to my post “…the hard part of building a SOA is not the technical details…it’s finding a appropriate services based on the business requirements…”. In addition I think that compared to how, relatively, easy it is to build a public service, although it may not be a properply designed one (whatever appropriate is in the relevant context), it’s far more complex to manage it. When you got your public service designed and deployed, how do you manage it over time? Versioning, extensibility, governance… And then we have the whole concept of processes (BPEL and such), how do you version and evovle a process, in runtime when it has X number of instances running in different stages with, of course, different state? [...]

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.

Creative Commons Attribution 3.0 licensed unless otherwise specified.