Power of Freedom & Flexibility: Going Cloud Agnostic
summary
Claims cloud-agnostic reduces long-term costs and enables portability while accepting higher upfront integration work and complexity. The team builds a platform that deploys Next.js apps across kubernetes clusters and public clouds, uses mongodb and minio for distributed storage, and swaps job buses between google pubsub and redis. Outcome: a globally distributed deployment engine with a distributed read-only cache and cross-cloud load balancing across AWS Google and owned k8s, yielding lower maintenance but requiring monthly migration testing and extra security work.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:55What cloud agnostic means
- 3:59Freedom and cost benefits
- 5:01Scalability and savings
- 6:02Picking the right stack
- 8:09Using abstraction libraries
- 9:35Embracing distributed architectures
- 10:37Building a migration plan
- 12:02Lyrid’s stack
- 13:48Live demo: cloud agnostic app
- 18:20Security and compliance
- 20:05Integration and monitoring costs
- 21:26Drawbacks and upfront costs
- 22:50Conclusion and design principles
- 23:33Q&A
related talks
26mCloud Agnostic Webscale
36mCloud-Agnostic Design for Fun and Profit
21mHybrid Cloud - nothing to worry about! 🌥️
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
29mCloud Agnostic Webscale
49mApplications architecture spanning multiple clouds
43m5 tips on creating modern, cloud native applications
36mPractical Cloud Native: What Works, What Doesn't