At my advanced age I'm thinking that these things should not drive me crazy, but they do. I’m reading an article a few weeks ago, all about this great company with a great need for a SOA. This company further discussed how they are looking forward to the "project" and wanted to announce their "SOA partner," a well known vendor.

So, what's wrong with that? Plenty!

First of all a SOA is not a mere "project" it's a way of doing something that really does not have an end. A project is something that has a beginning, middle, and an end, thus you can have a project that’s part of a SOA, but SOA is never a project. Get me?

Second, and something that sends my blood pressure sky high are those that pre solve their problems with a vendor. The vendor that they selected is a good technology provider, but assuming that they are the right technology provider before they even begin to understand their own requirements is a huge and stupid leap. Chances are you're going to select the wrong technology because once you understand your own problem, the check to the vendor has already cleared the bank. In some cases you’re getting rid of millions of dollars in hardware, software, and service costs that could be better spent in other places.

So, don’t call a SOA a "project" and don't select a "SOA partner" before you understand the problems you're looking to solve. Please send the money I'm saving you by giving you this very simple advice to your favorite charity in my name.

Posted by Dave Linthicum on August 30, 2005 10:53 AM