SOA 2.0 and why it doesn't really fly
You might have read about the tentative to create a new version of the Service Oriented Architecture dubbed SOA 2.0.
You might also have seen the rise of opposition to this new term on some blogs like Elemental Links or even an online petition to oppose this term.
The main rational for creating a new version of SOA seems to be :
With SOA 2.0, an event-driven architecture is deployed in which software modules are related to business components, and alerts and event notifications are featured. The initial SOA concept has not been event-driven but instead has featured direct calls from one piece of software to another in a client-server process, Natis said.
Well, that doesn't fly. What events are we talking about here ? In which way these events are different from asynchronous service invocations ? What about messages sent on an ESB like Mule or openESB ? Are they events ?
I would point to this article for a good example on how EDA and SOA can come together, without releasing a new architecture version.