This is the second part of a mini-series centered around cloud computing; a high-level overview of vendor lock-in and mitigation strategies. By Piotr.
Vendor lock-in happens when a customer is dependent on a vendor’s products or services and is unable to switch to another vendor without incurring substantial costs and/or organizational changes. This generic definition applies also to cloud vendor lock-in where cloud vendor is any public cloud provider like Azure, AWS, GCP, Hetzner, Linode, etc.
The article content covers:
- What is vendor lock-in?
- The Good - why single vendor strategy is attractive
- The Bad - putting all your eggs in one basket
Here are two most common pitfalls in avoiding cloud vendor lock-in:
- Using common lowest denominator
- Building your own integration layer
One of the most important benefits of using a public cloud provider are advanced services which can significantly improve developer productivity and lower complexity of IT governance.
In reality, things are very dynamic and every organization must be ready to react to the ever changing environment and requirements of the market they operate in. Good read![Read More]