It has frequently been observed that one can have an understanding of the philosophy of an SOA and the specifics of web service standards and still not know how to implement an SOA system that will provide lasting value to your enterprise.
Composite Software and BearingPoint, along with other contributors, have written a 2008 release book to help practioners to consider standards that come from practical experience in implementing an SOA. It is a practical book for the practitioner. The goal is to make the implementation of an SOA simpler and to encourage more people to deploy their own SOA. After all, today an SOA is considered an effective way to create an integrated system that implements a consistent architecture on a large scale, providing flexibility and agility across applications and data for long lasting.
BearingPoint, specifically shares our experience on how companies can organize their SOA strategies for success. A synopsis of our chapter proceeds:
"As you move from large applications to modular components, there are more interactions between the software components, and between the providers and consumers of the components. Assuming that components are smaller than applications, there will be more of them. And assuming that different components/services will be created by different people, then there is an organizational impact generated by a SOA."
Many times, the communication required to work things out actually improves design and avoids problems later. Your existing personnel are probably fine, they just may need to think differently, assume somewhat different roles, and learn a little. If you’re an organization manager and only read one chapter, this is the one.
To learn more, click here.




