How we support multi-cloud apps at Stack Overflow
summary
Stack Overflow runs Teams and Enterprise on Azure and the public site on GCP, so the platform team builds a layer that hides cloud differences using Kubernetes, Helm and Terraform. Infrastructure outputs become YAML published to GitHub and apps consume app-specific pipeline variables and cloud-specific overlays. Deployments use a Stack-flavoured CNAB invocation image (Docker image with Terraform, Helm and a Go CLI) built per release. Outcome: centralized infra definitions and a single pipeline, but developer overhead did not drop and the platform sits in a “messy middle.”
AI-written summary · about
chapters (10)
- 0:00Introduction to multicloud
- 1:34Stack Overflow architecture
- 4:48The multicloud problem
- 7:17Platform engineering approach
- 9:24Goals and early strategies
- 11:50Standardizing terminology
- 14:25Platform metadata strategy
- 18:58Invocation image and tooling
- 23:20Reviewing progress and goals
- 25:17Future plans and conclusion
related talks
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
21mKeynote: Panel: How Google and Microsoft are Using Cloud Foundry To Embrace Multi-Cloud
25mEnterprise Deployment to Azure and AWS in Azure DevOps
22mAppStack: An Open Source Cloud Native Platform for Running...
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
26mYes, One Can Simply "Terraform" Their App to Azure, Easily
46mUnlocking The Tech Wonderland: Combining GitOps, Platforms, and AI
01h 29mTutorial: Build Your Own Heroku With Cloud Native Stack