Navigating Consolidation in a Democratized Tech Landscape: Lessons from Booking.com
summary
Booking.com describes moving a 30-year monolith to cloud while keeping thousands of engineers autonomous, telling specific moves: centralizing secrets onto Vault and Terraform where teams initially used multiple homegrown tools, building a Kubernetes platform from a hackathon that now runs 4,000 services, and pushing golden paths (opinionated blueprints) to speed safe migrations. Migration pace is deliberately slow, success hinges on trust and product-market fit of vendors, and consolidation follows team-led adoption rather than top-down mandates.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:54Booking.com’s tech strategy and mission
- 5:27Shift from on-prem to cloud infrastructure
- 8:13Lessons from cloud migration journey
- 11:42Setting tech priorities for the year
- 12:22Organizational structure and team dynamics
- 15:29Benefits of small engineering teams
- 16:32Tooling and capability-based teams
- 18:38Consolidation in a democratized tech landscape
- 21:49Key factors in technology purchasing
- 23:12Vendor partnerships and adoption strategies
- 25:42Building connections for adoption
- 27:49Biggest lessons learned
related talks
26mInside Booking.com’s cloud center of excellence: Driving governance, scale, and cloud migration
46mBeyond DevOps: How and Why Companies Converge on Platform Models
30mChanging with HashiCorp at Mastercard Data and Services
35mPerforming Infrastructure Migrations at Scale
28mUnleashing Innovation by Unblocking your Developers
22mSimplicity: The Key to Software Success
28mMaking do: Scaling expertise on teams you can't grow
26mTen (Hard-Won) Lessons of the DevOps Transition