3 ms·
>In a few years down the line, you'll understand that you've lost the leverage you had to potentially take your public cloud business somewhere else when you ha
by EpicEng 9y ago
>In a few years down the line, you'll understand that you've lost the leverage you had to potentially take your public cloud business somewhere else when you have so many dependencies on Amazon tech
This is a non-issue for the vast majority of products. You do your eval and you chose what makes sense. Short of hiking prices by 1000% you'll never move anyway (this also applied to building ridiculous abstractions because "maybe we'll want to switch cloud providers someday!" No, you won't.)
- scarface74 9y agoOr "I'm going to put a facade over my database access because I don't want to be locked in to one vendor". Hardly anyone ever changes there database vendors just to save a few dollars.
- tracker1 8y agoIn 23 years I've worked on one project that moved databases. Client requirement, huge system that Oracle was the best match for. Also, one that was a licensed software that needed to support DB2, Oracle and MS-SQL to integrate with various state's agencies. The former was a huge pain, the latter was horrible to write code for. For the most part, you use what works for you and stick with it. The more risky a platform, the less you rely on features like stored procedures, etc. In the end, I'd rather have vendor lock-in than have to write complex queries three times, and other really cumbersome abstractions, slowing things down a lot! Extrapolating to services beyond the DB. In the end, the db migration was far less time/effort than maintaining an untethered software.