3 ms·
Also, the more you use your cloud vendor's various services in your code, the more subject you are to vendor lock-in. I won't name any names, but I'm pretty su
by bunderbunder 1y ago
Also, the more you use your cloud vendor's various services in your code, the more subject you are to vendor lock-in.
I won't name any names, but I'm pretty sure this is a big part of the reason why a specific cloud vendor pushed so very hard for us to push a bunch of data into their highly advanced NoSQL big data solution, when the data in question was perfectly happy continuing indefinitely to exist as a few tens of megabytes of CSV files that were growing at a rate of a couple kilobytes per day.
- jiggawatts 1y agoCosmosDB? It’s okay, this is the Internet, you can name names.
- bunderbunder 1y agoNaming names would not be helpful. The problem isn't any one company's business practices. The problem isn't necessarily even vendor lock-in. The problem is familiarity bias. When all you have is a hammer, everything looks like a nail. And, as a corollary, when you ask a hammer vendor what you should do their answer will always be to treat your problems like nails.