IMHO, SOA’s value proposition begins with the A in its acronym: architecture. There is sound, proven value in governing and growing a system’s architecture; there are also hard decisions that must be made, many decisions of which cannot be known a priori (which is why a process shaped around the rhythmic incremental and iterative release of executables is so important). There are many things we already know about what constitutes a good architecture and what does not. Stripped away of all the hype, a Service-Oriented Architecture is essentially a variant of well-proven message-passing architectural patterns.
- Grady Booch, “Snake Oil-oriented Architecture”
This is exactly what SOA should be about. Its not just services, its organization, its architecture. With all of the crap that we hear about how great SOA is, it is great to hear a grounded opinion about what we should care about.
Post a Comment