Blog Entry

Browse

Google App Engine and Open Source: What's in it for Us?

Written by Mike Gunderloy - Apr. 08, 2008

With yesterday's big announcement of App Engine, Google has become the latest big player to join Amazon, Sun, and others in offering some way to move your applications to "the cloud" - or more precisely, to someone else's servers. But what does this mean to open source software efforts? A little thought shows that the implications are decidedly mixed.

One thing for open source advocates to get potentially excited about is the language bias for the initial release of App Engine: it's Python all the way. Indeed, despite frequent press comparisons of App Engine to Amazon's AWS platform, the two are completely different animals. Google is essentially providing a Python-based sandbox with access to selected system services (such as email and authentication), while Amazon provides virtual computers on to which you can deploy practically any software you like. If you're putting together a Rails application, or anything else other than pure Python, App Engine is out.

Even if you are ready to work in Python, App Engine is not itself open source - nor does it ever seem likely to be. We don't know its origin for sure, but this certainly looks like a Google in-house project. Even if pieces originated with open source, Google has so far been careful to keep its own work covered by the "ASP Loophole" that we've discussed before.

On the plus side, App Engine offers the cheapest way to deliver software as a service - even open source SAAS - for applications up to a rather large size. You get roughly 5 million page views per month and 500MB of storage (which is just your application and its data; you needn't worry about the size of the operating system components) for free. Find more details in Stacey's post.

Putting a project on App Engine currently means accepting a sole vendor lock-in; if Google changes the terms of an account, or the service becomes unreliable (unlikely though that seems), you'll have no way to move elsewhere without a rewrite. By contrast, hosting with Amazon Web Services means that you can provision everything as a standard Linux server with open source databases, application servers, and so on. Moving from AWS to your own servers, or another vendor of virtualized hosts, is not an insurmountable issue.

Whatever direction you take towards making an application available "through the cloud" (and there are alternatives to Amazon and Google, including Bungee Labs, Morph eXchange, and Heroku), one thing is clear: we are in the early days of cloud computing. The competing models and incompatible APIs remind me strongly of the early days of personal computing, where each manufacturer's machines had their own operating system. I suspect that within five years we'll have a dominant model for this stuff, hopefully with portability between vendors. Until then, open source developers - like everyone else - will need care and a bit of luck to keep from ending up on a dead-end platform.

What are your thoughts on making apps available in the cloud?


Comments

Add Comment
  1. By Dave on Apr. 08, 2008

    One thing to keep in mind is that they were very specific that the actual service is language neutral and that they will be adding other programming language runtimes in the future. With their support for framework uploading to your site, the real lock-in is the database tier which is their proprietary Big Table database. If you did need to move from AppEngine to something else you'd have to build a brand new database and db access tier at the least.

    That said, as a web developer this is pretty exciting.

    0 Votes
  2. By gimprocks on Apr. 08, 2008

    Amazon seems to be the way to go - there's no lock-in, you can setup any environment you like and always move to another hosting environment if you're not happy with the service.

    0 Votes
  3. By adelph.us on Apr. 09, 2008

    This seems so very much like dark days of the Microsoft OS monopoly. Who can forget the memories of; stifled competition, and price fixing. In this case Google does the arm twisting AND knuckle cracking by dropping the pricing of a service to free. Goolge is using the advantage of massive scale built on the backs of consumers and media to choke the life out of them and any competitor.

    Do we now face a world where all apps are run on the google platform and coded to their specifications. Have we forgotten what happened to Borland, Netscape, and Novel.

    Make no bones about it; Google is trying to be the next OS at any cost. If they go on this path unchallenged we will see the snuffing out of a vibrant industry that was once the home of rebels that believed in the possibilities and the freedom of choice.

    It is also clear that Google is the biggest danger to Open Source software that we have ever seen. Where is the cloud/OS for those of us that want a choice and don't think its a good idea for one company to own the very life of the internet.

    We at adelph.us will be launching an alternative

    "You take the blue pill and the story ends. You wake in your bed and believe whatever you want to believe."

    "You take the red pill and you stay in Wonderland and I show you how deep the rabbit-hole goes. Remember -- all I am offering is the truth, nothing more."

    from the Matrix written by Andy Wachowski & Larry Wachowski

    0 Votes
  4. By friarminor on Apr. 10, 2008

    You gotta love Google. Without the GAE launch, there was slow spread of awareness for the alternatives like Morph eXchange despite completely open source in makeup.

    So make it quick- take the blue pill, adelph.us - there's certainly room for more.

    Best. alain

    0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.