Realtime websites with Django and Meteor
summary
A Django-based DDP server replaces the Meteor Node backend and pushes Django model updates over websockets using gevent, giving browser and mobile clients latency compensation with immediate local updates and server rollback on conflict. It relies on PostgreSQL listen/notify to broadcast commits (no extra infra), currently supports PostgreSQL only, has live-query work in progress, serves Meteor client files, and demonstrates Node-like throughput while keeping Django models, auth fixes, and predictable transactional consistency.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:17What is this project
- 1:46Latency Compensation
- 2:19No Schemer
- 2:53MongoDB
- 3:11Meteor
- 5:32Meteor Limitations
- 6:18Realtime Latency Compensation
- 7:24Python
- 9:52Asynchronous notification
- 10:32No new infrastructure
- 11:09Listen and notify
- 12:12Transactions
- 12:50Demo
- 24:58Question Time
- 29:40Django DDP
related talks
31mReinventing Django for the Real-Time Web
26mDjango 5.0: Elevating Experiences with Server-Sent Events – A Journey from Polling to Real-Time Vibe
38mButter smooth, interactive applications with Django...
25mOffline Django with Service Workers
26mUsing Django 4.2's StreamingHttpResponse and HTMX SSE to provide real time notifications
45mTWID Live
55mWorkshop 1 - Let's Make a Realtime Game with Django Channels
46mD3 + Websocket for Live Web Applications
