Immutable Infrastructure on Azure
summary
A bank-backed payment platform with 3.6M active users migrates to Azure and runs 90% of workload on AKS with 100+ deployment units, then redesigns for blue/green slots so each environment instantiates a full VNet, APIM, Application Gateway v2 and AKS; a custom deployer CLI generates ARM templates and automates provisioning; upgrades become low-risk with 10% canary traffic via Traffic Manager or Front Door (proof shows ~2 minute Front Door rollout versus three-hour in-place AKS upgrade) and a successful production switch.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:26Vipps infrastructure "evolution"
- 5:55[VCE] Vipps Core Engine
- 8:01[VCE v1] maintenance: upgrade AKS clust
- 9:55VCE v1 replace AKS cluster
- 11:44[VCE v1] upgrade AGW to v2
- 13:30[VCE v1] retrospective
- 16:40Mutable infrastructure
- 18:43VCE vNext requirements
- 19:36VCE vNext conventions
- 20:20[VCE Next] upgrade life cycle
- 22:57VCE vNext cons
- 27:01VCE next iteration requirements
- 29:06VCE infrastructure.AsCode()
- 30:59deployer infrastructure.AsCode() for VCE
- 38:11Azure load balancing options
- 41:24Priority
- 43:18Weighted
- 44:05Traffic Manager Lesson Learned
- 47:46Front Door Lesson Learned
- 48:33Wrapping it up
related talks
26mTransition to the Cloud Return
37mModern Architecture in the Cloud of 2026
50mPlatform Engineering: Creating Scalable and Resilient Systems
01h 01mDevOps with Azure Kubernetes Service
01h 00mEasier Deployments using a Green:Blue Strategy
47mUnleashing the Potential of Hybrid Cloud
53mInfrastructure as Code in Action! How to Build a Cloud Platform
01h 04mZero Downtime Application Deployments on Azure PaaS