You want to build out your SOA in an organized, thoughtful manner, and be ready to address the wide variety of concerns that come into play as you embark on your SOA journey.
Create an SOA roadmap.
SOA is a kind of architecture, or, rather, an approach to systems integration that represents a long-term strategy to realize an architecture. It takes a long time to build: as the SOA cliché goes, you can’t boil the ocean. Between figuring out services, security, registries, and repositories; performing vendor selection; getting an ESB running; and advancing to technologies such as business process management, rules, and service virtualization, there is a lot to do in one lifetime. To get a picture of everything you need to do and the order in which you need to do it that makes the most sense for your business, you need a roadmap.
A roadmap in general terms defines checkpoints along the path of a journey. So the first thing you need to know is what you want out of SOA. Where are you going? Why are you employing SOA in your organization? What benefits, in concrete terms, do you hope to realize? What is your target state? What is the dream architecture that you hope to have in place? Frequently cited reasons for implementing SOA in an organization include the following:
IT needs to be in step with the business, so that it can respond more quickly to changing markets and business demands. Services can help you realize this by promoting ...