Maximising Side Effects When Adopting Functional Programming
summary
bet365 moves an R&D team to Erlang to handle a business critical pub/sub publisher and a cash‑out service, building a POC in two months that sustains far higher load than the Java version (over 100k updates/sec, 3.5M topics, hundreds of thousands of clients), finds smaller simpler code, per‑customer failure isolation and much lower downtime, hands production services to ops where they run for years, and surfaces cultural lessons about training, sponsorship, measuring performance and avoiding “good solutions for the wrong problem.”
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:53Background - A Brief History of bet365
- 3:29It Comes Down to Our Culture
- 10:03We needed to Reinvent
- 14:47Our Mission
- 15:37And the answer is
- 16:39Erlang. Overview
- 21:36Erlang - The Functional Advantage
- 33:35AKA The First Big Sales Pitch
- 36:27Adoption Requires a Journey
- 36:57Adoption Requires Balance
- 40:06Widening Involvement - What happened?
- 50:44Maximising The Side Effects
related talks
43mBringing Functional Programming to Work
34mFunctional Programming: The Enterprise Edition
31mBuilding a Sustainable CodeBase with FP
01h 01mArchitecture Decisions: A Case Study -
41mA Decision Maker's Guide to Typed Functional Languages
39mConcurrency Oriented Programming In A Modern World
48mFunctional Programming: The Enterprise Edition
01h 00mKeynote: Over a Century of Programming