Real World Django Q&A
summary
Advice: start with Postgres, nginx/uwsgi and standard caches, optimize for developer productivity, and add monitoring early. When a site hits the wall the fixes are concrete: add short anonymous-page caching or Varnish, move heavy pagination into Redis (worked for a 100k‑page case), scale vertically then horizontally, and instrument SQL with pg_stat_statements. Avoid simultaneous cache invalidation by adding cache timeout jitter, centralize logs and metrics (New Relic/Graphite/Grafana) so triage is fast — centralized logging pays for itself.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:02Peter Baumgartner
- 2:27Optimize for Developer Productivity
- 26:38Postgres Logging
- 27:50Enable Pg Stat Statements
related talks
47mBuilding Scalable Web Apps
21mHigh-Availability Django
31mHigh Performance Django
47mHigh Performance Django at Ten: Old Tricks & New Picks
43mOptimize Python & Django apps with Postgres superpowers
21mBuilding maintainable Django projects: the difficult teenage years
35mCaching everywhere
52mData Driven Cache Invalidation