4 ms·
Vendors have already come up with a way to fight the vendor lock-in dodging that this article recommends: data egress charges. Whenever you are trying to take
by hota_mazi 8y ago
Vendors have already come up with a way to fight the vendor lock-in dodging that this article recommends: data egress charges.
Whenever you are trying to take your data out of one cloud into another one, you're going to be charged heavily, and these costs will likely exceed the costs of accepting vendor lock in and keeping your data housed in one location.
The only realistic way to fight vendor lock in is to keep your code as isolated from proprietary API's as possible (e.g. deploy containers, or use interfaces to isolate proprietary calls in your app).
- scarface74 8y agoAnd while you’re adding the extra complexity just to avoid lock-in, you’re not adding features that can acquire customers or get your existing customers to pay more. No, your CTO is no more going to uproot your entire infrastructure from AWS/Azure because you promised that it will be “seamless” than they are going to replace their six figure Oracle installation with Postgres because you used the repository pattern.