Last time I argued that from a technical perspective, the “server”, “client”, and “P2P” labels were complicated. That narrow view deliberately ignored the roles that these technologies have on the user, and on communities and business built around them.
I’ve been looking back at Paul Graham’s 2001 essay on “The Other Road Ahead.” He laid out a bunch of benefits that accrued from his successful company’s use of what he called a server-based architecture. While Viaweb originally relied on generic “Web 1.0” clients not distributed by his company, his essay looked ahead to richer clients such as what would come to be known as “Web 2.0.” I think the essay applies just as well today to mixed-technology deployments like Google’s current development. And I think it applies to some Croquet deployments, including those by my employer Qwaq. A lot of what Paul describes turns out to be things we’re already doing. But by explicitly identifying the benefits and what enables them to be realized, even a peer/client-centric geek like me can appreciate the operational value of the different technologies I’d mentioned last time. From this perspective, I’d say we’re “half-server-based.”
Worth a read (as are his other essays). See if you don’t agree.
