The Evolution of Tools and Services at Badoo
summary
Overview of the operational tooling and services used by Badoo’s operations team, including service discovery with Consul, container deployment choices around Docker and the challenges of selecting a scheduler/orchestrator, and standard log collection using the ELK stack. Discusses why some tools succeed or fail in an existing project and the practical difficulties of choosing and adopting new tooling in a live system.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:38Early infrastructure setup
- 8:11Puppet limitations
- 10:38Git binary files
- 13:31Git LFS and environments
- 16:48Tool selection
- 18:15Log collection in Docker
- 23:00Orchestration tools
- 26:55Service discovery with Consul
- 30:54Selling internal services
- 31:39Key takeaways
- 32:02Q&A
related talks
49mDocker in Practice: A Look at Its Use in Badoo After a Year
46mThe "Cloud" at Badoo a Year Later: Fixing Our Mistakes
48mIncident Management at Badoo
46m"The Cloud" at Badoo a Year Later: Fixing Our Mistakes
48mThe Sysadmin's Gentleman’s Kit
45mParallel Test Coverage and Other Elegant Ways to Speed Up Feature Delivery
22mPlatform Engineering at bol
53mChange your tools, change your outcome
