hardScenarioDesignSeniorStaff
When your infrastructure is heavily coupled to proprietary managed services, how do you design and execute a cloud provider exit strategy without obliterating the business?
2 min readUpdated 2026-08-15
Answer
Short answer
An examination of strategic foresight, the realities of vendor lock-in, and the technical necessity of abstracting proprietary dependencies during a large-scale migration.
Was this answer helpful?
Likely follow-ups
- How would you resequence the migration if the vendor announces an unfavourable pricing change with only 90 days' notice?
- What would make you decide a specific proprietary service is not worth migrating away from at all?
- How do you validate that the anti-corruption layer hasn't quietly become its own new form of lock-in?
Related questions
- How do you execute the Inverse Conway Maneuver on a 200-person engineering org that accidentally built a distributed monolith mirroring their dysfunctional silos?hardAlso on engineering-leadership3 min
- A better embedding model has come out. What does moving to it cost you?hardAlso on migration5 min
- How do you conduct a post-mortem after a catastrophic Sev1 outage triggered by a junior engineer's mistake, without succumbing to the blame game?hardAlso on engineering-leadership2 min
- How do you force product leadership to prioritize paying down toxic technical debt in a hyper-growth scale-up that only cares about shipping features?hardAlso on engineering-leadership3 min