Migrating a Monolith to the Cloud
summary
Etsy performs a lift-and-shift of a 14‑year monolith to GCP in roughly eight months, using terraform for infra-as-code and extensive pre-cutover testing that simulates 2x simulated holiday peak load. Teams hit gotchas: terraform destroys on load‑balancer edits, a DNS provider accidentally directs traffic to GCP, and a 0.01% tail latency spike in the GCP load balancer that requires Google collaboration. Two cutover attempts (one rollback) lead to a six‑hour successful maintenance window; live tuning uncovers CPU, MySQL mutex, and network tail issues.
AI-written summary · about
chapters (4)
- 0:00Start
- 7:30How on earth do we migrate?
- 10:25Things we learned really quickly
- 25:32Upcoming challenges
related talks
36mHow we finally migrated an eCommerce-Platform to GCP
48mThe Journey of a strongly coupled Monolith into the Cloud Land
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
46mHow Back Market Rebuilt Its Platform by Changing Cloud Provider
21mAvoiding That $1M Dollar AWS Bill - Mark Michael, Glenn Oppegard
40mConsiderations for Migrating Enterprise Workloads to Google Cloud Platform
21mMoving into the cloud
27mFailover Without Fear: A Practical Guide to Active-Active...