Programming Google App Engine: Build and Run Scalable Web Apps on Google’s Infrastructure

You have visited several times. Please consider leaving a comment. Thanks for visiting!

This entry was posted on Saturday, May 15th, 2010 at 6:04 am and is filed under Internet. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “Programming Google App Engine: Build and Run Scalable Web Apps on Google’s Infrastructure”

Guy McArthur on May 15th, 2010 at 7:43 am

This is a great, and fairly in-depth, guide to the Google App Engine API’s. It presents both Python and Java API’s on equal footing. Navigation through the book was very clear and straightforward whether you want to take the Java or the Python path. The development environments are presented as well. This book will be most useful if you are already familiar with web application development and just need a tutorial with simple examples for how to do this type of programming on the Google App Engine framework.
Rating: 4 / 5
Robert Hancock on May 15th, 2010 at 9:54 am

I’ve worked with the App Engine for about six months and have gained most of my knowledge from the online documentation. I wish I had had this book when I started. This is the best explanation I’ve seen of entities and how they relate to transactions. The code examples in Python and Java are extremely helpful and give great insight into how the two languages approach the App Engine abstractions. The sections on data modeling and Django integration are particularly good. Not only did this book fill in gaps in my knowledge, but it is sufficiently detailed that I’m sure I will keep it on my desk as a reference. I’ve tried the other App Engine books and this is by far the best. If you have any interest in the App Engine, start here.
Rating: 4 / 5
ivy league scientist on May 15th, 2010 at 11:58 am

I think the book does a great job at explaining Google App Engine. There was no “technical fluff” added to the book which I always appreciate. By “technical fluff” I mean unneeded text which should be looked up else where like in documentation. Also, I found the book very easy to follow and found I could manage to jump around from one chapter to another without reading the book linearly. For example, I was able to read the 1st chapter and a half and then jump to the Django chapter and get a sample Django 1.1 app with the admin interface live on App Engine without much trouble.
Rating: 5 / 5