DjangoCon 2008 Keynote: Guido van Rossum
summary
Google App Engine runs HTTP-driven web apps on Google hardware with a free tier and hard limits: 1 megabyte limit per request/item, 10 seconds per request with ~300ms CPU encouraged, ~10ms datastore RPC and <1ms memcache. The platform forbids writable files, raw sockets, subprocesses and C extensions for sandboxing, and uses a nonrelational datastore (no SQL joins), so Django’s ORM and admin don’t work natively; developers bundle Django 1.0 or use App Engine’s template fork (Django 0.96). Demo deploys a working “shout” app, datastore viewer and interactive console; billing, large file APIs and batch jobs are planned.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:43What is App Engine
- 3:52How App Engine works
- 6:07App Engine Architecture
- 11:32Scaling
- 15:43Replication
- 16:38Datastore
- 18:45Security
- 26:16Next languages
- 30:07App Engine
- 35:42Zips
- 37:39Google App Engine
- 40:25Demo
related talks
01h 22mWhat is Google App Engine?
01h 25mWhat is Google App Engine?
43mSPONSOR WORKSHOP / Charlie Engelke/ Google
31mWeb API Mashups in a Python Application
01h 06mEffective Django
28mDjango MiniConf: Lightning talks
30mFrom Zero to 200 OK in 30 Minutes: Web Development with Django, Heroku...
23mµDjango, an Asynchronous Microservices Technique with Practical Examples
