Google App Engine Preview Release

Tuesday, April 8, 2008 by Mistlee

Can't see any images? - Click To View!

Click to Play

Twitter Unleashed
WebProNews is proud to introduce a newcomer to the Video Department. After extensive searching, we couldn’t believe the most obvious candidate was right...

Recent Articles

Adoption-led Market Or Shareware/Trialware?
I just got a chance to read Simon & Zack's individual replies to my question whether an Adoption-led market was very different from a Shareware market. I actually liked Simon's definition, but felt it was missing...

On The Go With Buzz
A couple of weeks ago, I met Luke Razzell at the social media cafe in London. Luke is CEO of i-together, the UK company behind Blog Friends, one of the more useful applications for Facebook. What Luke...

Don't Develop In The Absence Of Customer Feedback
Chances are, that if you've been involved in the creation of software or any kind of product, you've probably heard the advice: "Don't develop in a vacuum". A vacuum is a space that is essentially empty of matter...

Startup Developer Superstar Detection
Background... In the early, early days, a large part of whether a startup succeeds comes down to the founders: Do they get along? Are they committed? Are they nimble? Do they make intelligent decisions?

Facebook Limits Applications' Linking
Facebook applications can be bad enough when they're upfront about their identities; getting tricked into installing them is the last thing (aside from various privacy violations) that any user needs.

With Software, Sometimes Less Is Less
There has been a lot of discussion on the web about the value of simplicity in software. Generally, I agree with the notion of simpler being better (all other things being equal). But rarely are all things equal.


Google App Engine Preview Release

By Philipp Lenssen

There's big and seemingly good news for web developers today: Google released the Google App Engine.

This invite-only service - you'll be added to a waitlist if you sign up now - aims to bring the benefits of the Google infrastructure to all developers. It's somewhat similar in spirit to Amazon's "Elastic Compute Cloud" efforts; instead of managing your own servers and worrying about scaling, upgrading and traffic spikes, Google says with the App Engine, they'll be "dynamically providing computing resources as they are needed," and you just write the code. Google argues the App Engine "makes it easier to scale from one user to one million by taking advantage of Bigtable and other components of Google's scalable infrastructure."

Google App Engine programs are implemented using Python, Google says (a neat choice, I think; Python is an elegantly simple, and usually nice-to-read language). Note that Google's programming environment you can download to your computer simulates the Google App Engine, but you need to install Python first. You can then also utilize components for authentication, sending emails, or fetching other URLs. Another component called "webapp," along with the Django templating language, can be used as a wrapper to create web sites.

Here's a video show-casing a "hello world" sample application created with the App Engine:

(A sample chat application as part of the Application Gallery is live as well, though it didn't work for me.)

Download a Free Trial of Ektron CMS400.NET

And what's in it for Google Inc? (Looking back to other now semi-canceled efforts, like the Google SOAP Search API, this is also interesting in terms of pondering the longevity of this service.) One goal for Google in the "near future," as they say, is to offer a paid service once your cross certain scaling limits. Another goal may be to standardize web apps in their favor; using the Apps Engine, it's only a small step to use the integrated libraries to switch to a Google Account for authentication for your site. And the more sites make use of the Google Account, the more powerful that account will become. Google writes:

Your application can allow a user to sign in with a Google account, and access the email address and displayable name associated with the account. Using Google Accounts lets the user start using your application faster, because the user may not need to create a new account. It also saves you the effort of implementing a user account system just for your application.

And who knows, maybe in future releases of the App Engine, using other services by Google - like their advertising framework - will also be made temptingly easy. Instead of just being one of the web's most successful players, perhaps Google continues trying to manufacture the board game itself. A Google layer in-between HTTP and the end user, with the potential to "tax" activity on that layer with micro-payments (e.g. the Google Checkout service) or Google ads (e.g. the AdSense that come with the Google AJAX Search API).

[Thanks Colin Colehour!]


About the Author:
Philipp Lenssen from Germany, author of 55 Ways to Have Fun With Google, shares his views & news on the search industry in the daily Google Blogoscoped.
About ApplicationDevelopmentNews
ApplicationDevelopmentNews is a collection of news and commentary designed to keep you in step with the ever evolving landscape of Application Development.

ApplicationDevelopmentNews is brought to you by:

-- ApplicationDevelopmentNews is an iEntry, Inc. publication --
iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509
2008 iEntry, Inc. All Rights Reserved Privacy Policy Legal

archives | advertising info | news headlines | newsletters | comments/feedback | submit article

Unsubscribe from ApplicationDevelopmentNews.
To unsubscribe from ApplicationDevelopmentNews or any other iEntry publication, simply send an email request to:
ApplicationDevelopmentNews News Archives About Us feedback