Django and More on Google App Engine with App Engine Patch

I’ve recently had the chance to play with Waldemar Kornewald’s “Google App Engine Patch” and have come away very impressed. All LittleShoot Google App Engine (GAE) projects now run on it for a couple of simple reasons:

  1. Seamless Django integration (including 1.0.1)
  2. Thorough documentation
  3. Healthy open source development community with an excellent steward in Kornewald and frequent new releases

The Django integration got me first. Almost everything works, such as manage.py, Django authentication, Django testing (the original reason I switched), etc. There are also lots of other goodies in there, like support for boto’s SQS module. If you’re unfamiliar with it, boto SQS allows you to call Amazon’s Simple Queue Service (SQS) from Python. That’s a huge step in getting around GAE’s limitation on longer lived, CPU-intensive tasks. Just queue it up in SQS, and your GAE app will keep humming along fine — cloud integration at its finest.

To get started with App Engine Patch, download the zip file from the home page and work off the sample project. The download includes App Engine Patch itself as well as the sample project.  

With Django App Engine Helper not supporting Django 1.0 and seemingly inactive, App Engine Patch is a godsend and gets a huge thumbs up.

Great work Waldemar, and don’t forget to donate.

Advertisements

6 Responses to Django and More on Google App Engine with App Engine Patch

  1. […] and loading Dojo from Google’s AJAX Libraries API.  For Google App Engine Patch, see my more recent post.  This area changes quickly, so check the dates on any blog posts you’re looking […]

  2. Amre Ellafi says:

    You made me happy, i lost passion towards GAE lately !

  3. Thanks a lot for blogging about app-engine-patch! We really need more people who help build a community.

  4. adamfisk says:

    My pleasure Waldemar. It’s really helped me out quite a bit, so thank you. The community seems to be growing just judging from the mailing list traffic, and I think it will only get bigger as App Engine grows. There’s probably a solid business to build around it if you were so inclined.

  5. Interesting suggestion. Hmm, haven’t spent much thought on making an App Engine + Django support business, probably because I’d rather build web/mobile apps myself, but who knows. Building a startup and making it successful is very difficult. 😦

    One of the reasons why we originally decided to release part of our code was because django-helper introduced a new model class. We didn’t want this splitting the open-source community and making code sharing difficult (one group would derive from db.Model and the other from django-helper’s model class). Another reason was that we were very unhappy with how difficult it was to get started with Django on App Engine.

  6. adamfisk says:

    I hear you Waldemar. I’ve found that a lot recently — good business ideas that would probably be successful, but that just wouldn’t be that much fun to run! If you can create a business that will be both successful and fun, that’s the way to go of course. That’s what I’m shooting for too — heck you only live once and all.

    You could actually be very successful using App Engine Patch to help stir up interest in your startup too, depending on the business. I’d expect use of App Engine Patch to go up significantly, especially when App Engine comes out of beta. Heck, Google might even buy it up. I definitely think you’ve got something here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: