Sports Betting Evolution
summary
A betting platform's evolution from a PHP/Delphi monolith to microservices is described, migrating frontend, middleware, and core in stages so legacy users stay on the old stack while new users use the new one. Engineering choices include Aerospike as the wallet store for atomic high‑load balances, Kafka for odds distribution (reducing stale prices from ~20% to ~2%), and .NET Core microservices on Kubernetes for fast autoscaling, with a target of 1 million calculations in 5 seconds and peak loads around 3.5k bets/min and 5k transactions/min.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:52Product and tech evolution
- 10:24Monolith to microservices
- 16:50Tech stack and architecture
- 21:50High-load architecture
- 27:12Cloud scaling
- 30:08Migration and future plans
- 44:00Q&A
related talks
44mAn Evolution of a Betting Engine at William Hill
40mDistributed Computing challenges in the gaming & betting industry
43mIntro to Stateful Services
47mAll-In on Innovation: The Winamax Poker Platform
25mFrom Millions of Customers to Petabytes of Data: A Journey to Microservices
35mFrom Monolith to State-of-the-Art Banking
15mArchitecting Scalable Platforms for Financial Wellness
42mFrom Monolith to Microservices: The Evolution of a Banking Platform
