Common SOA/Integration project pitfalls and how to avoid them
Continue Reading September 1st, 2009 Jorge Balderas
Your team has designed the perfect architecture for an SOA (Service Oriented Architecture) project. You are all excited and ready to get rolling. A few weeks later you find out that you will need to make several compromises in your design because of other teams’ skills and constraints. Your end of the integration is almost fully developed and ready for integration testing when you find out that the other end is still undergoing development, or worse, it is in still on early stages of design. Sound familiar? I have found these to be very common situations in SOA integration projects that span across two or more teams and/or applications. In this post I will explore five frequent SOA project pitfalls along with some recommendations that can help mitigate or avoid some of these roadblocks to make your project successful. You will find that these scenarios are not unique to SOA integration projects, but they also apply to most inter-group IT projects.
