My interview with Frank Martinez, CTO of Blue Titan software is now available at IT conversations. I had some good conversations with Frank in NY in May about Web Services protocols and thought others might enjoy hearing his thoughts about them as well. I was particularly intrigued that Blue Titan was actually using things like WS-Policy inside its software, not just talking about how they might be used, or enabling their use by others. Frank maintains that the architecture of his middleware platform eats its own dog food and is built using the same technologies it enables.
As Doug Kaye explains in the editor's note, this isn't a light introduction to the topic of Web services middleware. We pretty much dove right in. Even so, I think you'll find it interesting and understandable if you're familiar with Web services and the idea of Web services middleware.
In the interview, we talk about what Web services intermediaries are and how they work. One of the questions I asked Frank was how a CIO knows he needs a Web services intermediary. Frank believes that the inflection point occurs when a company is moving beyond merely incorporating a few Web services standards here and there in the application development process and is beginning to align business and technology strategies with service orientation. Another key indicator is when your Web services are starting to have reach in terms of numbers, geography, and user types.
I think Frank's right on in this advice. The only thing I'd add to it is that you ought to understand what a Web services intermediary is well before these points and work one into your ultimate plans and architecture.