Lessons Learned from Five Years of Multi-Cloud
summary
PagerDuty runs the same services across AWS and Azure for about five years to hit a hard 50 ms latency requirement, deploying ~50 backend services across 10 teams on EC2 equivalents. Tooling is Chef (migrating to Terraform) with Chef containing ~50–100 provider-specific code paths, and data is self-run MySQL/Cassandra clusters rather than RDS — the team hires DB experts. Result: fewer visible cloud outages but big costs in right‑sizing, networking gotchas (NAT timeouts, ICMP blocks, BGP leaks, fiber cuts) and substantial operational overhead.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 3:55Defining multi-cloud
- 6:12The journey to multi-cloud
- 12:38Benefits of the approach
- 17:43Challenges and lessons learned
- 26:10Strategic considerations
- 30:06Q&A session
related talks
31mDevOps in the Cloud: Case Studies of Amazon.com teams and their resilient architectures
27mDevOps in the Cloud
43mGetting to a Multi-Cloud Deployment - A Case Study of
43mMigration to the Cloud, DevOps Perspective
01h 08mPerformance testing in the cloud
01h 03mContinuous Security in the Cloud
33mGoing MultiCloud
28mReliability Lessons from Running High Traffic Services for More Than 10 Years