As I’ve discussed many times, SOA is not a product.  It is an architectural style.  That said, products can help leverage and encourage SOA.  Gartner expects there to be some pretty significant growth in these products over the next few years. 

There is no silver bullet here.  When you buy a product from a vendor (including Microsoft), you are buying more than tools. You are also buying the constraints that drove the assumptions in the tools.  Those constraints are important, and usually overlooked.  kingkong-snow-globe

This is what makes it so difficult to compare the SOA offerings from different companies.  If you buy a product that assumes a particular platform, or practice, then your company will have an easier time using that product if that platform or practice are already in place.  For example, if you buy a product that assumes you manage your IT portfolio as such, but you don’t manage your IT portfolio, it will be more difficult to get value out of your purchase.

As you may discover, SOA can have a large impact on your organization, including changing your planning and funding mechanisms, or a small impact which changes your tools.  How big you can go, depends on what your business will get from it and how well you have aligned business sponsorship. 

So when you decide to move to SOA, you will inevitably have to pick some tools and products to empower your implementation.  In that process, look to insure that the vendor can tell you how to get from where YOU are to where THEY want you to be.  Is that destination where your organization wants to go?  Can you get in for a low cost?  Can you measure value?  If your choice doesn’t let you answer these questions… why pick it?

  • Buying a tool that you don’t use… that’s bad.
  • Buying a tool that forces you to make expensive changes to your process before you see value… that’s worse.