It seems a good time for Manifestos, that’s taken for granted, but do we need to wrap the SOA approach into a Manifesto too? Now that the technological benefits of SOA applications over existing legacy applications have been well documented? Now that it is well known that SOA offers business benefits across applications and platforms, including location independent services, a loosely coupled approach providing agility, the dynamic search for other services, and that services are reusable?
According to Joe McKendrick, “SOA is not a thing that you do, and it definitely isn’t a thing that you buy … but something tangible, a style if you will, just as Roman, Greek or Modern are styles of architecture.” This perfectly paraphrases the very first statement of the SOA Manifesto, which philosophically states that service orientation is more an attitude, “a paradigm that frames what you do.”
The good thing about the Manifesto is that it reminds us of the cultural implications of a SOA approach. And that it plays nicely with the principle that states that “SOA is not made out of products”. But on the other hand we should not neglect the technical challenges, of course. Because the situation we are focussing on is the fact that over 50% of the processing in the current application landscape is background processing.
That is why we need interfaces that guarantee the inclusion of background processes into the SOA business process. That is why we need intelligent Workload Automation tools based on Web Services to initiate, monitor, and manage background processes. And that is why UC4 customers prefer an Automation Broker (here is the Whitepaper for Download) to bridge between SOA vision and batch reality than being part of a platonic style symposium.
I am looking forward to your comments!
Here is the video of the announcement:
You can find a complete list of the authors at the bottom of the manifesto, or view a picture of everybody on stage at the signing of the SOA Manifesto.