"Using Multiple Databases in Django Applications"
summary
Real project details: Django moves from one database to separate configurations and customer data databases because the quotes workflow drives ~85% of DB reads; a DB router plus explicit using() calls route reads/writes, local dev uses logical DBs, and migrations run per database. Deployment splits data with a dump and points both connections at the same instance first, then flips with zero downtime migration; tests (~3,000) and read replicas validate it.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:58Why multiple databases
- 9:13Planning the split
- 12:47Django database routers
- 17:22Testing and deployment
- 21:04Final architecture
- 22:52Key takeaways
- 23:34Q&A
related talks
11mMultiple Backend DBs In A Rails Application
27mMigrating legacy data to your Django project
30mMulti-tenancy strategies with Django+PostgreSQL
57mDjangoCon 2008 Panel: Schema Evolution
32mContinuous Deployment and Release of Django Apps
24mOf Django, PostgreSQL schemas, and your multi-million dollar idea
30mUsing Multiple Databases with Active Record
29mScaling Django to 500 apps