“Web 3.0 will ultimately be seen as web applications which are pieced together.”- Eric Schmidt
In the wake of Google’s AppEngine announcement, I want to remind you of this video I’ve posted before: Eric Schmidt talking about Google’s vision for the Web 3.0 computing era.
To me, AppEngine seems like the most logical evolution of Google Gadgets! (This is what everyone thought Eric was talking about back in that video.)
The Real Story
However, every story written about Google’s newly launched AppEngine has incorrectly correlated this new service to Amazon’s EC2 and S3 services.
I think these people are way wrong and that if the Silicon Valley echo chamber wants to make up a competitor for AppEngine, its proper correlate (by a whisker) is Facebook’s F8 platform. If you must cram this new service into a pigeon hole, think of AppEngine as the Facebook Platform for the grown-up web.
Why isn’t AppEngine like EC2 & S3? Constraints, constraints, constraints.
Google is going the run-time environment route, not the scalable, “put anything you want in a box and we’ll scale it” route that EC2 provides. Case in point: we could run the BricaBox Platform on EC2 by tailoring our own environment (the LAMP stack) and booting it up on Amazon’s servers. We could not get BricaBox running on AppEngine without re-writing in Python, ditching functionality which needed outside libraries or languages, or relational databases.
Google is not trying to provide pure utility here, they are trying to provide utility tethered to their infrastructure. While EC2’s initial investor pitch was “we have this scale and want to monetize unused portions of it,” many smart people called them out for what they were really doing: creating a new business based on the concept of utility computing, which had nothing at all to do with their core infrastructure at Amazon.com (i.e. they weren’t using EC2 or S3 for their needs).
The point about tying it into their infrastructure, however, is an important one. Google is clearly looking to have as much of these apps tie into existing pieces of Google’s infrastructure: everything from the authentication systems (Google Accounts only!) to code libraries (most open source or API accessible code from Google is written in Python and ready to run in their environment) is based around this infrastructure and will be based around this going forward
So, why is AppEngine more like the Facebook Platform 3.0?
AppEngine is designed for lightweight apps
AppEngine apps are wrapped around Google’s existing userbase and communication infrastructure (Gmail), creating a more organic Social Ecosystem for Google
AppEngine is way more inter-operable with the rest of the web than Facebook apps, though still built around a proprietary stack (Google’s runtime env is the equivalent of FBML)
The first AppEngine apps will be huge! The next ones will have just as much trouble emerging from the murky waters of the web as any other apps