Connecting Patients to Doctors in Real-Time Using Django
summary
Built a real-time patient→doctor matching system using Django, Celery, Redis, Websockets that routes only to doctors licensed where the patient is, supporting about 52 queues (states, DC, territories). Doctors push into per-state Redis queues; matches pop and are validated, with a priority queue used to avoid duplication across multi-state doctors. A Redis-based lock prevents simultaneous acceptances (race found during a free two‑week trial). System scales and offloads async work successfully.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:00Product overview
- 3:01Technical challenges
- 4:41Licensing and state rules
- 7:01System requirements
- 8:46Initial solutions and flaws
- 11:39Celery and AJAX polling
- 13:27Websockets and real-time
- 14:36Managing doctor status
- 18:13Atomic call acceptance
- 20:09Final system architecture
related talks
38mButter smooth, interactive applications with Django...
25mOffline Django with Service Workers
31mReinventing Django for the Real-Time Web
55mWorkshop 1 - Let's Make a Realtime Game with Django Channels
29mBuilding real time applications with Django
34mRealtime websites with Django and Meteor
28mThe Doctor Will See You Now: Machine Learning for Telehealth
22mDjango, Python, and Health Care Data