Multi-Cloud & On-Premise, Let's Cross Borders! Get the Best of Both Worlds
summary
Presents a concrete pattern for multi-cloud and on-premise infrastructure: factor infrastructure into reusable Terraform modules per provider and service, and pair each module with a cloud-specific SDK adapter in a Python abstraction layer consumed by a single Lambda-style handler so business code uses logical names. Demonstrates a local and AWS demo (S3/object storage via Boto3) and explains the approach is portable to Azure, GCP, OVH and Scaleway, while noting operational constraints such as Kubernetes’ frequent releases (~every 3 months) with about 14 months of support and risk of breaking changes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:13Why choose multi-cloud
- 6:42Kubernetes vs cloud-native
- 13:28Hexagonal architecture challenges
- 22:06Modern approach with common core
- 33:08Demo and code abstraction
- 39:48Conclusion
- 40:31Q&A
related talks
14mMulti-Cloud Foundations with Terraform
38m50 Shades of Multi-Cloud Infrastructure
15mCloud infrastructure best pratices in a multinational corporate
15mPaaS isn’t enough: your internal platform in Multi Cloud
55mSelf-service infrastructure is no longer a dream
15mJourney to Hybrid Multi-Cloud
53mProvisioning Cloud Infrastructure+Terraform
30mHow Sunrise Banks Built a Symmetric Multi Cloud Architecture with Terraform & Vault