Slow Food Digests Better - or how to maintain a 8.5 year old Python project without
summary
AMO is a 13-year-old site ported from PHP to Python/Django 1.1 in 2010 that now serves 3 million weekly users from a roughly 250,000 LOC codebase. The team avoids a full rewrite, incrementally modernizing the backend (Celery, RabbitMQ, Elasticsearch, moving from Django 1.6→1.8 cost ~3 months) while replacing the untested frontend with a React single-page app and controlling rollouts with feature flags (waffle) and heavy unit and QA testing.
AI-written summary · about
chapters (13)
- 0:00Introduction to legacy projects
- 1:14Speaker background and project history
- 3:48Early PHP and CakePHP era
- 5:59Transition to Python and Django
- 8:29Zamboni and early Django years
- 12:38Firefox Marketplace and legacy code
- 13:23Olympia project challenges
- 16:41Incremental improvements strategy
- 17:27Modernizing dependencies and tools
- 21:05Frontend rewrite with React
- 21:46Lessons learned and best practices
- 27:20Importance of QA and testing
- 29:17Final advice and closing remarks
related talks
36mA Python Takeover
36mA Python Takeover
35mFrom Dinosaurs to Snakes - Decomposing the Enterprise Monolith
47mBuilding Scalable Web Apps
18mPython in Our Home: (R)evolution Yesterday, Today and Tomorrow
45mPython at Massive Scale
27mHow We Migrated 3.8 Million Lines of Python 2 Without Interrupting Deve...
26mProtoype for Production