|
The early application of SOA governance increases the assurance that the SOA will remain on track as it expands. That expansion can be an increase in the number of services, an increase in the number of applications using a specific service, or all of the above. Either way, SOA is a beehive, and it's important to get the swarm under control.
It's never too early to enact SOA governance measures, just as it's never too late. But the earlier you get started, the easier it is to evolve the SOA in precise alignment with business objectives.
It's really all about knowing when, where, how, and by whom services (and any other artifacts of the SOA) are being created and used. It's also about knowing with certainty that those services are earning their keep.
Ultimately, it's about knowing how all the pieces fit together, about having a thorough understanding of the relationships and dependencies that connect services to applications to business processes -- everything in the SOA food chain.
Obviously the earlier you have the necessary visibility, traceability, and information, the better. You're then better equipped to make good decisions about next steps.
<P>
You'll find more information on SOA Governance at bea.com/soa-governance. |
