Inside Booking.com’s cloud center of excellence: Driving governance, scale, and cloud migration
summary
Booking.com migrates its Terraform footprint from on‑prem Terraform Enterprise to Terraform Cloud, moving over 3,000 workspaces using robust migration scripts and a phased pilot approach, cutting operational headcount cost by about 75% and dropping ticket load from ~300/yr while keeping state backed up to S3. Challenges include lack of per‑team organizations (forced a one organization workaround), missing CLI for sensitive vars, early VCS integration instability, and gaps in observability that prompt close collaboration with HashiCorp.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:10Why migrate from Terraform Enterprise
- 6:49Pre-migration environment overview
- 9:17Motivation for change and goals
- 12:55Post-migration architecture
- 15:01Organizational challenges and fixes
- 16:26Migration strategy and process
- 20:42Lessons learned and improvements
- 22:05Future plans and benefits
- 23:51Outcome and cost savings
related talks
30mNavigating Consolidation in a Democratized Tech Landscape: Lessons from Booking.com
30mChanging with HashiCorp at Mastercard Data and Services
37mRoad to Domain Driven: The Reckless Life of a Cloud Engineer
46mEverything you need to know about cloud migration
34mCloud Native Transformation: How Ticketmaster is Changing Culture and Speeding Up
11mFuture-proof your business to drive growth and transformation
22mOrganising a fast growing DevOps team a real life use case
19mHow We Built a DevOps Dojo to Upskill Our Organization in Terraform