The benefits of adopting a service-oriented architecture are well-known: reduced integration costs, greater asset reuse and the ability for IT to respond more quickly to changing requirements. But getting the most out of an SOA implementation requires diligence and thought. First, target systems that people are used to having applications built around. Don't take interoperability for granted, and before committing to a technology platform, identify all information sources and make sure to document how each system defines data. Expect some trial and error, budget realistically, and consider providing incentives to stakeholders for giving it a try. Make sure to have clearly documented policies and procedures for every aspect of the SOA development cycle. And realize that SOA will add to the network load--proper network design also calls for modeling performance.
Learn more about best practices for building an SOA infrastructure:
- read the article [1] at BPM Today
ALSO:
- read this [2] on whether SOA will help or hinder the alignment of business and IT
- this [3] on whether SOA will work in your environment
- this [4] on the basics of SOA
- this [5] on the four stages of successful SOA
- and this [6] on taking it slow with SOA deployments
Links:
[1] http://www.bpm-today.com/story.xhtml?story_id=112006N1CDWW
[2] http://www.fiercecio.com/story/will-soa-help-or-hinder-the-alignment-of-business-and-it/2007-02-22
[3] http://www.fiercecio.com/story/does-soa-work-in-your-environment/2007-01-31
[4] http://www.fiercecio.com/topics/soa.asp
[5] http://www.fiercecio.com/story/the-four-stages-of-successful-soa/2006-12-19
[6] http://www.fiercecio.com/story/take-it-slow-with-soa-deployments/2006-10-13