~/talk

Scaling Django: Mastering Database Routers with AWS Aurora

Talkat DjangoCon US 2026 · 2026-08-24..08-28· [databases, cloud-infrastructure]
slides:none on file

OneBlinc moves Django reads to Aurora’s read endpoint and keeps writes on the primary via a simple Django database router that maps DB-for-read to a read-only endpoint and DB-for-write to the writer, forces migrations and locks to the writer, and treats relations as allowed. Replication lag is typically 10–20 ms, reader nodes carry 60–70% of traffic, writer CPU drops to ~15%, and failover/promote completes in under 1 minute; autoscaled readers handle payday peaks and cut the DB bottleneck.

AI-written summary · about

  1. 0:00Introduction and speaker intro
  2. 1:11Company background and team
  3. 3:25Database overload problem
  4. 8:09Why choose AWS Aurora
  5. 11:57Database routers explained
  6. 15:25Solution idea with read-only endpoint
  7. 18:30Key implementation insights
  8. 24:00Cost and optimization tips
  9. 27:36Lessons learned and scaling challenges
  10. 31:06Future possibilities and alternatives
  11. 34:37Q&A and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.