SOA - more then just hype

It is amazing how much talk there is from different vendors about Service Oriented Architecture (SOA). Unfortunately I have to agree with Richard Turner - most of the it is just marketing talk. SOA is an abstract notion - it is not linked to products or vendors, it should be generally applicable to any given distributed systems platform.

Richard puts it even a little bit harsher "The whole SOA/ESB thing is all hype, people! Once you come to realize and accept that, the world becomes clearer. You don’t believe me? Define what SOA is. Then try and find one other person that agrees with you wholeheartedly. If you’re lucky enough to manage this, try and apply your definition of SOA across more than one platform / technology. Repeat for ESB. Good luck!" (See

Does SOA Exist?

) but he also sees the advantages of Service Orientation.

I think the general concept is quite interesting but I'm not really sure when I will ever see an actual implementation of SO design. I recently took a look at FABRIQ recently - which combines service principles, one-way multi-transport messaging, queuing networks and ideas from autonomous agents into a single framework. Fabriq is no services framework but does show the complexities involved when creating a complete SO design. The Microsoft Patterns & Practices group has also published an “Enterprise Development Reference Architecture” which also provides some interesting guidance but which I think is quite complex as well.

If you want to know more, check out these interesting postings about SOA lately:

On SOA, Indigo and Services

Just what is an ESB, anyway? Part II

Web services standards can sometimes inhibit SOA development, some say

Radovan responds re SOA

SOA revisited (again)

Call increases for SOA clarity

Does ESB Exist?

Does SOA Exist?

The SOA reference model

What does SOA really mean? One big hype machine

"SOA" doesn't really exist, does it?