3 ms·
Because they did an analysis of what was offered and what it cost and determined it was the best fit. Coupled with the fact that it’s run by the company with th
by c0pium 3y ago
Because they did an analysis of what was offered and what it cost and determined it was the best fit. Coupled with the fact that it’s run by the company with the best reputation in tech for backwards compatibility and you have a pretty compelling case.
Also AAD.
- redwood 3y agoBackwards compatibility in connection with the headline above is interesting
- wongarsu 3y agoThey are giving two years notice. With a clear migration path with step-by-step instructions (linked in the article). And since MariaBD and MySQL are more-or-less drop-in replacements of each other it should also be a painless transition for most. That's not perfect, but much better than when last year GCP retired IoT Cloud Core with just one year notice, a much less public announcement (an email to affected customers and a note on the product page) and no clear migration path.
- mastax 3y agoTwo years' notice is more of an Apple-like deprecation timeline.
- amtamt 3y ago> since MariaBD and MySQL are more-or-less drop-in replacements of each other Not anymore for a while, unless application developer has been very careful in using DB features. Also, there are things like how indexing differs in two. If ORMs have been used, without a good DBA being available... there are many landmines on the migration path.
- squigz 3y agoI think this is an interesting take people have on large companies in general, but tech companies specifically - as though everything they do is perfectly planned and executed, and is the most reasonable course of action It might surprise some people to learn that companies are made up of humans, who have various biases, and are subject to various pressures - like politics and bureaucracy - to produce certain results. Not every decision they make is inherently going to be the best decision