Challenges in developing a large Django site
summary
Lanyrd is a Django site that sends about 3,000 emails a day using signed JSON unsubscribe links and uses signed cookies to avoid per-page session lookups; fragment caching keys include a conference.cache_version integer to invalidate templates. Redis stores follow and attendee sets for fast set intersections (Redis handles ~100,000 ops/sec) and Solr indexes sessions, slides and 20,000+ speakers for faceted and “appears with” queries. Assets are minified, SHA1-hashed, pushed to S3/CloudFront so deployments can ship assets before code; major challenges are safe HTTP fetching, production profiling and zero-downtime schema changes.
AI-written summary · about
chapters (12)
- 0:00Tricks & challenges developing a large Django application
- 5:00Signing uses
- 6:43Signing in Django 1.4
- 10:53Bulk Invalidation
- 15:19Our redis sets...
- 22:20Benefits
- 24:53Talking to an API?
- 26:40Safe URL consumption Connection timeouts
- 28:00Debugging in development rocks!
- 33:32Django Improvements
- 37:21Read-only mode
- 40:19Global settings are BAD
related talks
42mA Nice Problem to Have: Django Under Heavy Load
29mHow Django helped us make a better conference website
53mDjango: a Data Shovel With a Future
47mReal World Django Q&A
23mLessons Learned in a Large Django Project
26mBuilding and Scaling an AI Startup with Async Django
28mLightning talks
22mLearnt lessons in a big Django Project