A long time ago, in a galaxy far, far away, I worked for a company briefly owned by the IT research firm Gartner. During that time, I spent a lot of time hearing about Gartner's Hype Cycle.
If you're not familiar with the Hype Cycle, it describes the love/hate/adoption cycle we -- the press and technology workers -- go through with new technologies. They are:
At first, I thought it was excessively obvious. But as I've followed technology over the years, I've seen the wisdom of the hype cycle. It's easy to forget that what's out of vogue today will return.
I mention this because, it seems to me, Web services is sloshing its way through the Trough of Disillusionment. I've seen several articles of late about how SOA and Web services need to be divorced. That may be true, but the tone implies that SOA -- at the height of its hype cycle -- is somehow so-much-better-than Web services. I've also seen a lot of criticisms about the volume of Web services standards.
But it's important to remember that just because a tech is in the low part of its hype-cycle, that doesn't mean it was "just a fad" or not worth your time.
In fact, those using Web services are probably just settling down to figuring out how it works in the real world, as this blogger points out. (Though I think he's a wrong about how he sees the hype cycle.)
Over on the .NET Developer's Journal, blogger Frank Cohen offers a defense of Web services, particularly as the technology applies to SOA. He explains how these technologies complement each other. He also relates how companies are using SOA in conjunction with Web services to quickly create composite applications, thus giving these companies a strategic advantage over those who choose to focus on building more direct interoperability between services.
But if Web services is to move out of the trough and on to everyday usefulness -- and I think it inevitably will -- then advocates are going to have to address the problem of too many standards.