Analysis of Google Wave

June 8, 2009

Radovan Seman?ík’s Weblog published “Storm Alert”, a quite interesting discussion of Google Wave. You must read his write up here. Among the points I noted were:

  1. Lack of security
  2. Inconsistent nomenclature
  3. Assumptions about performance when there are large numbers of users.

For me, the most telling comment in this article was:

Google Wave architecture does not adhere to architectural best practice. It is not minimal. The robots are described to communicate with Wave by HTTP/JSONRPC (robot is server), Client apparently communicates by HTTP (as AJAX application?) , while the wave federation protocol is described as XMPP-based. Why do we need so many protocols? Is there any reason why robot protocol and client-server protocol needs to be different? The non-minimalistic approach can be seen in the OT operations as well. The antidocumentelementstart and endantidocumentelementstart operations seems redundant to me. If they are not redundant, their existence should be explained in the architectural documents.

Highly recommended. In my opinion, Wave is a variant of the dataspace technologies. Like the first Searchology, I think Google built a demo and rushed it out the door in order to blunt the PR impact of Microsoft’s roll out.

Stephen Arnold, June 8, 2009


2 Responses to “Analysis of Google Wave”

  1. Helical Wave » Analysis of Google Wave : Beyond Search on June 8th, 2009 8:15 am

    […] original here: Analysis of Google Wave : Beyond Search Extra […]

  2. Steve on October 3rd, 2009 12:50 pm

    I found some Google Wave invites, hit me up

  • Archives

  • Recent Posts

  • Meta