Do modern cloud applications lock you in?
summary
Claim: lock in equals multidimensional switching cost not just specific managed services. Provides five approaches: criticizes cloud service-to-service mapping and universal wrappers, shows DynamoDB atomic append forced a rewrite with composite keys when porting, notes an app ported in two weeks when velocity and automation are high, cites AWS pace of ~3,000 feature launches per year and EKS extended version support, recommends three workable levers: managed open source, increase delivery velocity, and capture design intent and patterns to reduce real switching cost.
AI-written summary · about
chapters (9)
- 0:00Introduction lock-in concerns
- 2:54Defining modern cloud apps
- 9:17Switching costs dimensions
- 14:12Abstraction layers limits
- 21:01Options complexity tradeoff
- 28:34Managed open source benefits
- 32:36Velocity reduces switching costs
- 39:25Patterns beat mental lock-in
- 41:58Good software engineering best defense
related talks
26mWhen and Why Does Portability Matter? Exploring Multi-cloud, Open Source and Cloud Switching Costs
27mDon’t put all of your APIs in one cloud
30mThe transformative power of modern applications
43m5 tips on creating modern, cloud native applications
33mThe elephant in the cloud: Strategies of cloud cost optimisation
17mModernizing Cloud-Based Infrastructure with Secure, Scalable, and Efficient Solutions
33mWhat the Cloud?
19mCuring Addiction Is Easier