Marrying Django and FastAPI 💍
summary
FastAPI runs alongside a synchronous Django process on the same host, sharing the same database and Django models so migrations and the admin remain intact; repositories isolate all ORM access and convert Django instances into Pydantic domain models, letting FastAPI handle async webhooks and high‑IO uploads. The team uses domain‑driven structure, keeps tests synchronous at repository level and async at route level, uses a single sync_to_async adapter point, and migrates with zero downtime. FastAPI adoption rises from 14% to 25% (2021→2023).
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:56What is FastAPI and why async
- 7:12Existing architecture and challenges
- 9:41Migrating to Django async
- 11:53Marrying Django and FastAPI
- 14:25Compromises in the marriage
- 18:24Domain-driven design approach
- 22:39Repository-level compromises
- 24:53Technology choice is not binary
- 26:40Q&A session
related talks
24mCombining Django ORM & FastAPI in a Data Visualization Tool
28mThe promised Django Land; the tale of one team’s epic journey...
40mTaking Django Async
21mBuilding Powerful APIs with Django, Django Rest Framework, and OpenAPI
46mCreating Solid APIs
26mDjango at
25mTaking Django's ORM Async
29mBuilding real time applications with Django