Banking with Django - how to not lose your customer's money
summary
Holvi runs its core on Django + Django REST Framework, PostgreSQL, Celery/Redis and AWS and prevents lost money by treating payments as durable messages. The system records an outbox row inside the same DB transaction and sends only on on_commit + Chronos retry, receivers store into an inbox with a DB unique constraint to deduplicate; Kafka is optional for pub/sub. At ~10k payments/day this cuts manual failure cases from five a day toward zero; reconciliation and Datadog/Sentry alerts hunt bugs.
AI-written summary · about
chapters (9)
- 0:00Introduction to banking with Django
- 3:42Holloway business model overview
- 6:54Payment processing flow explained
- 10:27Reliability at different scales
- 13:57Reliable messaging with outbox model
- 20:45Handling programming errors and monitoring
- 24:40Scaling reliability for banking
- 25:25Closing remarks and thanks
- 25:47Q&A session
related talks
40mZero-downtime payment platforms
26mMaking Django Really, Really, Ridiculously Secure (CW)
32mOutpace Your Competition: Banking Solution Thrives with Scale and Security
41mProduction Django: Building a Highly Scalable, Secure Django Site
15mPlatform Engineering for FinTech
53mFuture Banks Live in The Cloud: Building a Usable Cloud with Uncompromising Security
32mEnhancing Security, Reliability, and Global Scalability in FinTech
32mChoose Your Own Django Deployment Adventure