Data & state
Databases, schema changes, caches, and background work: everything that remembers.
Django code is stateless; the state lives in PostgreSQL, Redis, and the queues Celery works through. Each of these needs its own capacity planning, backups, and failure plan.
The topics here cover the database, schema changes, caching, and background jobs, which between them cause many of the hardest production problems.
- PostgreSQL & databases104 guides
Connecting, pooling, tuning, and troubleshooting the database behind Django: mostly PostgreSQL, with MySQL and SQLite.
- Migrations & schema changes30 guides
Applying Django migrations safely during deploys, and repairing migration history when it goes wrong.
- Redis & caching31 guides
Caches, sessions, and Redis itself: what to cache, where it lives, and what happens when memory fills.
- Celery & background jobs46 guides
Running work outside the request: Celery workers and Beat, Django tasks, queues, retries, and monitoring.
211 topic memberships across the area; a guide can belong to more than one topic.