Google I/O 2009 - Offline Processing on App Engine...
Why Stack Overflow recommends it
Stack Overflow users link it when they need the official explanation of App Engine task queues, including how queueing differs from pub-sub and from cron jobs.
Recommended by 2 people across 2 different months, 2009 to 2010.
What it is
A Google I/O 2009 session by Brett Slatkin on where Google App Engine was heading beyond request-driven web apps. It introduces the task queue and executor model for offline computation and walks through interesting applications of it.
What people said
Recommends mcotton · 2009-06 · Stack Overflow · on “Google App Engine - Task Queues vs Cron Jobs”
I didn't understand the differences very well until I watched the Google I/O video where they explain it. The official source is usually the best. [this video] slides from the presentation [LINK]
Recommends nulltoken · 2010-11 · Stack Overflow · on “How to implement a light pub-sub service on App Engine?”
During his Google I/O 2009 "Offline processing on App Engine: A look ahead" presentation ( video [this video] , slides [LINK] ), Brett Slatkin presents the Task Queue service. He states that Pub-sub systems maximize transactions, decoupling: Large numbers of small transactions per second One-to-many fan-out with changing receivers Guaranteed ordering, filtering, two-phase commit And specifically emphasises Our new API implements queueing, not pub-sub I'm interested in only a subset of those functionalities: One-to-many fan-out with changing selected/fixed internal receiver handlers Guaranteed ordering , filtering, two-phase commit Targeted goal would be to ease publishing of notifications/message
Cites Andriy Drozdyuk · 2009-11 · Stack Overflow · on “Is Google App Engine better than Webfaction for a beginner in Django dev?”
Webfaction : Plus: Great shell access. Ability to install python modules, or anything else you might need. You will love checking out source code from shell to update your production (no need for FTPing anything anymore!) Very good performance and reliability Great support + wealth of info on help knowledge base and in the forums. (FORGET bluehost or anything else you ever tried). I was surprised by amount of answers I found to what I thought would be difficult questions. You can use regular database and you can do joins (see app engine minus #2) Minus: Setting up initial deployment can be a bit tricky the first few times around (as is to be expected from shell). Growing-scaling can be expen