|
|
The more I think about what service oriented architecture means the more I realize loosely coupled has to go beyond lip service.
Organizations as much as architectures must be decoupled, so they can
be remixed. Its just so much horse manure to talk about SOA without a
formal commitment to loose coupling. That is, open documented
interfaces across granular components or services, with no funny
business and hidden calls. Interoperability is not just a marketing
term. You can't have SOA and attempt to drive lock in.
The
more I think about the problems of SOA the more its clear the culture
of a company will be as important in delivering it, from a vendor
perspective, as any set of technical assets. Monoliths are not service
oriented. But, we can't break them down without freedom of
disassociation.
-- James Governor, RedMonk
|
|
|
