![]() |
|
|
Weekly Review: Web Services New Tree in Same Forest
August 27, 2002: In this week's commentary: In 1999, pioneering providers clung to the ASP tree. Now a bigger band is reaching for the Web services tree, not realizing the forest is the key discovery.
It's human nature to want some certainty in an uncertain world, and one of the ways we achieve a sense of certainty is by naming things. We feel that we have some control over something once we can put a label to it naming turns the unknown into the familiar.
But sometimes, premature naming can lull us into a false sense of security. A misapplied or inadequate label may mislead us as to the true nature of a thing, lending an aura of validity and permanence to ill-conceived first impressions.
The Buzz That Was ASP
Give us your feedback in the ASPnews Discussion Forum
This was partly naivety on my part, not realizing how defining the sector and quantifying the market opportunity was a requirement for securing meaningful venture capital funding. I fondly imagined that venture capital investment was about taking risks, and that this meant investing money in a sector before anyone can safely define and size the market opportunity. But it seems that many investors at the time were looking to win risk-premium rewards for investments that they imagined to be risk-free, and so the industry's startups needed to present an image of certainty, even if none existed.
Looking back with the benefit of hindsight, I think I was right to be wary of defining the term prematurely. That early insistence on defining application service providers helped create the schism that later sprung up between outsourcers and net-native ASPs, who went on to form their own Internet Business Service Providers group. At the same time, it crystallized people's thinking about ASPs solely in terms of outsourcing existing applications, whereas the more interesting developments came when software developers created new generations of web-delivered services.
Three Years Later and No Consensus
I was reminded of all this recently when I noticed that people are starting to debate what we really mean by the term Web services. They're saying the term is too vague, that it encompasses all kinds of services delivered over the Web, when it should be used in the much narrower sense of specific application services founded on a recognized set of industry-endorsed protocols.
Albeit with the best of intentions, this search for orthodox respectability risks channelling Web services into a self-created ghetto, cut off from the most vibrant and exciting exponents of the technology through over-eagerness to adopt a neat and tidy definition, sanitized to be acceptable to the enterprise market and to venture capital investors.
I have an image in my mind of successive bands of explorers wandering through a huge, marvelous forest, trying to work out which tree they should be looking for, not realizing that what they've discovered is the forest. Three years ago, a group of them came looking for the ASP tree, and now a larger band is trying to locate the Web services tree. All the while, they're wandering among the limitless possibilities of a network that connects computers, software, businesses and users together in a single, seamless universe. And still they can't see the forest for the trees.
Phil Wainewright founded ASPnews.com in 1998 and is the publisher of Loosely Coupled. He can be contacted at
Back to Analyst Columns |
|||||||
|
|
Featured
Links |