Mythology of Service Orientation
When I attended Gartner's "Business Process Management" summit this March, I was struck by the immaturity of SOA. Most of the sessions and discussions were at the level of "what is SOA" and "how to get started with SOA". This is a concept that is 8+ years old in the fast moving high tech world. Something the vendors have been pushing for 3+ years. Why has there been so little adoption if SOA makes so much sense?? Why is it still a new and/or poorly understood concept??
I'm doing a CTO presentation on Monday and I'm going to make the following points. What do you think of these Myth and Realities of Service Orientation?
Myth/Reality
M: SO is a technology or set of technologies
R: SO is an architectural paradigm for building distributed systems
M: SO is revolutionary
R: SO is evolutionary
M: SO is the end goal
R: SO is a means to an end
M: SO requires business and technology overhaul
R: SO can and should be an incremental process
M: SO is complex
R: SO is easy
Microsoft's goal is to build interoperabilty ala XML and Web Services into all of our products. It's about incremental improvements in a heterogeneous world, not selling an ESB.
Thoughts??
-Kevin Boyle, the "other" SoCal Architect Evangelist
