Posted by: Dilipkrishnan
when relevant content is
added and updated.
Recently I ran into this post from Arnon of DDJ fame which is in response to another response by Sam Gentile :-). I wrote about this in related posts a while back and this seems to be a recurring theme in many discussions. Seems like both are trying to say the same thing that “SOA is all about the business”. but I can’t help but add my 2 cents to this discussion
This (SOA) has nothing to do with business drivers. It has to do with defining components, relations, attributes on relations and components as well as constraints.
By the way, SOA has nothing to do with technology either. You can implement SOA using WS-*, Atompub, MSMQ, CORBA just as much as you can implement REST with quite a few technologies.
Putting those two statements together means SOA has nothing to do with technology nor business!!!
On a serious note tho’, its my opinion that the “relations, attributes on relations and components and constraints” are all business level components, relations between them, attributes on relations and components and constraints. SOA is a way of thinking about (read architecting) your applications and how they interact with and compose with each other to provide business value. How this SOA is “applied” has nothing to with the business… well yes it does, but not in a direct way.
To take an analogy of building a house. The notion that the house needs to have a certain set of properties like good ventilation, good sun light, access to different rooms etc is akin to what an SOA lays a blue print for. Now which wood/ paint/ nails etc to use to build (read appling SOA); i.e. achieve that vision is only material to the builder (read solution architect/developer) not the home owner (read business stake holder). The home owner only cares about the “business” constraints/attributes. I’d say SOA s all about the business!