Don’t put all of your APIs in one cloud
summary
Argues that vendor lock‑in is real but manageable, citing the 2017 S3 outage: 11 hours and startups burning credits then facing sudden high costs; recommends concrete measures: package services in containers for portability, adopt Terraform for provisioning to keep one language across providers, prefer open‑source standards (Postgres, Kubernetes), treat APIs as the glue, and design continuous disaster‑recovery/anti‑lockin processes rather than a one‑time migration.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:20Welcome
- 2:19Adrien and Remy
- 3:28The main issue
- 4:39The cloud
- 5:53The market
- 7:04French and European ecosystem
- 8:55Diversification
- 12:32Availability
- 15:16Containers
- 18:15Automation
- 22:03Multicloud
- 24:02Conclusion
related talks
25mBuilding APIs in a Cloud Native era
43mAre Open APIs Enough to Prevent Lock-in?
05mGeorge Reese interviewed at OSCON 2010
07mLightning Talk: Why APIs Matter in the Multi-Cloud Strategy
43mDo modern cloud applications lock you in?
56mBusy Architect’s Guide to the Cloud Offerings
45mWhat We Need Are Standards in the Cloud
41mHow convenience Is Killing open standards