Building Multi-region CI/CD Pipelines with a DevOps Mindset
summary
N26 moves from a single EU region to multi-region CI/CD by decoupling config from code: application never contains region logic, deployment simply swaps region/environment. The team replaces SaltStack-managed service vars with Terraform modules and a Consul service-backed key/value for runtime endpoints, enabling environment changes without redeploys. This supports migrating ~90+ microservices across EU and US (growing from 3 to 6 environments) while shifting provisioning ownership to service teams and removing SRE bottlenecks.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:53Deployment pipeline
- 5:40N26 Infrastructure
- 13:53Framework Injection?
- 15:53Infrastructure layer?
- 19:57Remember the 12 Networking Truths...
- 21:20Introducing Terraform
related talks
17mMulti Region Deployments with AWS CI/CD and Terraform
37mMoving from 1 to N regions: an open retrospective
35mMulti Region Terraform Deployments
37mThe Nth Region Project: An Open Retrospective
33mContinuous Deployments and Data Sovereignty: A Case Study
23mCI/CD at Scale: Best practices with AWS DevOps Services
01h 03mContinuous Security in the Cloud
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks