The "Cloud" at Badoo a Year Later: Fixing Our Mistakes
summary
A retrospective on Badoo’s cloud-like platform covering its overall architecture (creation history, load distribution, fault tolerance), script log collection and indexing, and a Google App Engine–based queue parser. It reviews problems encountered, future plans such as phproxyd in PHP and control logic in Go, and proposes a modern reimplementation using Go and Tarantool.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:09Cloud system origins
- 3:41Legacy cron problems
- 5:08Cloud architecture design
- 8:20Cloud components & performance
- 10:07Scheduler optimization with Go
- 11:55Load balancing approach
- 13:45Master server failures
- 16:15Script timeout handling
- 18:06Post-launch features & logging
- 20:43MySQL for queues & transactions
- 22:54Queue workers
- 25:10Downtime incidents & lessons
- 28:47MySQL performance issues
- 31:42Replication & connection limits
- 33:10Future plans & Go adoption
- 36:03Q&A
related talks
41mThe Evolution of Tools and Services at Badoo
49mDocker in Practice: A Look at Its Use in Badoo After a Year
48mIncident Management at Badoo
29mBowerbirds of Technology: Architecture and Operations at Less-Than-Facebook Scale
49mServing 30,000,000 Requests an Hour in the Cloud
28mCloud in your Cloud
46mHow to Enable 100 Million Logins Without Downtime ...
48mRewriting Parse.com for scale