With the platform-as-a-service revolution getting into full swing, developers (especially in start-ups) have more options for creating and deploying applications without the hassle and more extreme cost of setting up and maintaining infrastructure.
Dion Hinchcliffe at ZDNet compares Amazon's approach to providing infrastructure services to Google's. He found that Amazon's set of services is more flexible but not as integrated as Google's App Engine.
(Credit:
Dion Hinchcliffe, ZDNet)
What if you realized that you didn't want to host your application on Google App Engine anymore? Good luck; almost everything you are given access to is proprietary--that means all your data is locked into BigTable in a format that isn't like a traditional relational database. It's also very tempting to use the APIs Google provides to interface with things like Google accounts.
On top of that, you will be using the "Webapp framework" that Google built that makes writing Python applications really nice--but good luck porting that to another language or putting it on a machine of your own.
On the other hand, Google is just trickling out its platform-as-a-service with support for Python. Support for other languages will follow. Whether Google would support other databases in its cloud remains to be seen.
Google's announcement of its App Engine has naturally generated a lot of buzz, as well as some fear, uncertainty, and doubt. There is the concern that Google will corral even more user data via its App Engine, becoming a kind of 21st century data and advertising baron, as Microsoft has been the operating system and productivity software baron in the last three decades.
If you extrapolate from Google's growing share of search and advertising, and include a growing share of Web applications through its APIs and the fledgling App Engine, you could imagine a Google that becomes the dominant Internet operating system and infrastructure provider. It's still the early days of cloud computing, but the ground is shifting.
"It's funny that we waged the war to free ourselves of (the) shackles of Microsoft and Hailstorm (a failed attempt to manage personal data)," said David Young, CEO of cloud infrastructure provider and App Engine competitor Joyent. "Now, for some reason, the digerati are anxious to run into exact same thing with Google. It's not evil, but they are tracking users and clickstreams, which (are) the real currency of the Web, and most people don't care. If you can get all data, you can target ads and the user experience, such as showing a site in a different color, depending on user profile."
The Web currency of user data and clickstreams is also vital to Joyent's business. The company has 10,000 customers, handles 5 billion page views a month, and provides infrastructure for 25 percent of the third-party applications running on Facebook. Through its Player's Club, Joyent provides free hosting to Facebook developers, as well as OpenSocial developers, in exchange for the data.
"We gather the data and work with ad networks to help their clients target sites," Young said. Joyent works with ad networks such as Slide, RockYou, Social Media, Federated Media, and AdBrite. "With billions of visitors, Google can gather the data on its own, but the social networks allow companies like Joyent to get access to it as well," he said. Basically, the majority of developers are willing to share their user data in exchange for free infrastructure services.
David Young, CEO, Joyent
(Credit: Joyent)"If I were Google, I would buy every big Web application, such as Six Apart and WordPress, out there to get access to clickstream and user data as people move across the Web. I think that is what App Engine is all about," Young said.
In light of App Engine, Joyent is offering a similar infrastructure service (but using MySQL, Postgre SQL, or Oracle databases rather than Google's Bigtable and file system). Like App Engine, the Joyent "Garden of Eden" program includes free infrastructure for Python Web applications in exchange for customer information and clickstream data.
However, Joyent isn't limiting the usage, and it will provide unlimited compute, storage, memory, and bandwidth, as well as root control. Google's App Engine, which is in beta, is limited to 500MB of storage, 200 million megacycles of CPU, and 10GB of bandwidth per day. Young figures that this would support 25,000 unique users a month, while Joyent will support a million users for free.
With all the hand-wringing about Google's increasing footprint and clout, the company is contributing code to the open-source world and driving data portability standards, such as the OpenSocial and Social Graph APIs. David Recordon notes the potential for App Engine sites to log in via Google Accounts.
Today that means that every App Engine site could have a shared sense of a user; the ability to understand who someone is across different App Engine sites and Google services. (Obviously I'd love to see Google move toward supporting OpenID for this sort of thing, but small bits piece by piece work for me.)
Imagine if Google Accounts added support for the (upcoming) OpenSocial REST APIs. All of a sudden, each of these App Engine sites could start injecting activity and querying for activity across each other. Maybe you'll argue that this just means that Google Accounts could become the next big social network, but isn't it a bit different when this functionality is just a part of your hosting infrastructure? What if Google Accounts ignored the notion of friends and instead left that to actual social networks? If done right, this really could be the first shipping glimpse of the distributed social Web that there is to come.
If Google's growth trends continue to accelerate, the company will colonize more Web territory, collecting more data and monetizing it across billions of users and sites. So far, Google has a head start, with its highly profitable search and ad business (which is why Microsoft is in hot pursuit of Yahoo) and is moving into new application territory.
The old guard--Microsoft, IBM, Hewlett-Packard, Dell, Sun Microsystems, Cisco Systems, Oracle--haven't yet revealed plans for colonizing Web users with end-to-end, cloud-based platforms. They have stood by while Salesforce.com becomes a company with $1 billion in annual revenue. Will they be standing on the sidelines as Google and others, such as the 22-person Joyent, prove the viability of cloud platforms as a service?
Software pioneer Dave Winer knows about disruptive technology. He was instrumental in formulating RSS, XML-RPC, OPML, outliners, and podcasting.
Dave Winer
(Credit: Dan Farber)Here's part of what Dave had to say about Google's App Engine, a foray into making its infrastructure available to developers.
Now, what Google announced is really exciting! I'm not kidding. It's even better than I hoped. Yes, it's only Python, but IBM's PC-DOS was only BASIC and Pascal when it first came out, and it didn't matter. Yeah, I preferred C, but I coded in Pascal because that's what you had to do to get an app running. What you're going to see here that you've never seen before is shrinkwrap net apps that scale that can be deployed by civillians. That's a mouthful, but that's what's coming. Why? Because here is a standardized platform that can be stamped out in the billions of units. Maybe Google can't do it, but the perception is that they can. Who is willing to stand up and say Google hasn't nailed scaling? What PCs did in the 80s, Google is doing now. PCs took the black magic out of owning a computer. Now Google is taking the black magic out of operating a scalable web app. Python is the new BASIC.
Marshall Kirkpatrick of ReadWriteWeb considers, as I did, Google's dominant position in selling ads online and how App Engine could amplify that dominance:
The point is, Google App Engine may be neither competitive nor monopolistic - it might just be trivial as Google Pages or Google Base. So far it seems pretty simple and useful, though. We'll have to take a deep breath, hope that Amazon and others step up their offerings a notch or two in response, and see what the future brings.
Clint Ecker of Ars Technica also notes a potential downside in Google's App Engine:
Perhaps the most blatant downside is being locked into Google's platform. Existing projects will have to be ported or written from scratch, and those that rely on traditional relational databases will probably have difficulty making the transition. Even more difficult would be transitioning your application to your own servers if you choose to leave Google's tender embrace. Once you've created an established application on top of Google's authentication service and stored all your data within the company's datastore, removing all this code and data and moving it to another location would appear to a be fairly onerous task.
It's still early in the platform-as-a-service sweepstakes. But the signs are clear. As Nick Carr pointed out in his book The Big Switch, the large clouds will cover the planet with computing infrastructure. Amazon has to be more motivated to improve its Elastic Compute Cloud, and big players like Sun, IBM, Oracle, Microsoft, Yahoo, and others will also be inspired to open their clouds to developers. But as Dave pointed out, we are in the BASIC, embryonic days of platforms-as-a-service.
- prev
- 1
- next





