How we finally migrated an eCommerce-Platform to GCP
summary
Lift‑and‑shift migration moves an entire e‑commerce platform to GCP using Terraform and Ansible on plain GCE VMs instead of GKE, with HashiCorp Consul service discovery plus Nomad, pgBouncer, Prometheus/Cortex, HAProxy and Kafka. The runbook migrates 200 microservices, 138 databases and 5 TB of data onto 119 GCE instances, completes the cutover in 6 hours 25 minutes (Kafka partition reassignment finishes in 50h50m), and preserves traffic routing via prepared Consul queries.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53Migration challenges
- 3:39Lift and shift approach
- 5:05Service discovery with Consul
- 18:27Cross-data center lookups
- 24:55Kafka migration strategy
- 27:27Migration execution plan
- 32:45Results and achievements
- 34:11Infrastructure as code
- 35:16Q&A
related talks
27mMigrating a Monolith to the Cloud
46mHow Back Market Rebuilt Its Platform by Changing Cloud Provider
24mFrom Lift-and-Shift to K8s: A Two-Phase DevOps Modernization
39mHow GCP Helped Me Save My Production at Mamie’s
40mConsiderations for Migrating Enterprise Workloads to Google Cloud Platform
31mA Journey of Migrating Data Platform from Data Center to Cloud
35mExperience from the field - how customers migrated from Google Cloud IoT Core to Eclipse Hono
48mThe Journey of a strongly coupled Monolith into the Cloud Land
