If we interact by sending and receiving messages then we are doing SOA, right?

 

Why don’t we just call it ‘messaging’ then? Why the hyperbole?  

 

The problem is that we aren’t talking about Service-oriented communication or Service-oriented programming – we are talking about Service-Oriented Architecture.

 

Here is my opinion -  yes, messaging is the underpinning of SOA. Yes, you don’t have SOA without messaging. Yes, it is about providing services to consumers via standards-based interfaces. Yes, messages and schemas and contracts are important.

 

But, SOA is not just about messaging.

 

SOA is about a vision for the (virtual) enterprise. It is a progressive effort to manage the complexity of enterprise application portfolios. It is about providing a clear model for integration inside and across organizational boundaries.

 

What does this mean you ask? Marketing fluff?  I think not – more to come.