Re:Azure dropping database support for MariaDB. Users advise...
by alwaysrunning on Saturday September 30, 2023 @11:11AM
(#37716182)
in comparison Azure depreciated Azure classic VMs in 2014 and just last month stopped letting customers run them. If it takes you more than two years to plan and migrate a DB your likely not running it on MariaDB and if you are there are plenty of consultants that can migrate your apps back end in less than two years. Hopefully if you are running a db you are also backing it up so the idea that data is being destroyed is a bit dramatic.
Re:Azure dropping database support for MariaDB. Users advise...
by mpixel on Saturday September 30, 2023 @12:38PM
(#37717126)
There also other cloud companies to depend on that have been more sane. I doubt that in practice this will cause huge insurmountable challenges, but it's a headache and not a ton of fun.
Re:Azure dropping database support for MariaDB. Users advise...
by yawaramin on Saturday September 30, 2023 @01:59PM
(#37718025)
If you are willing to let two years pass by and then allow your database to get completely deleted, why wouldn't you rather take a small hit on delivery of some other projects in six months, possibly face a small amount of downtime, and migrate away so you get to keep your data?
Re:Azure dropping database support for MariaDB. Users advise...
by amtamt on Saturday September 30, 2023 @03:40PM
(#37718982)
Who knows if one would still be working in this project/ team/ company?
Nobody gets good raise/ promotion for maintenace or migration work. Some pat on the back... May be.
Re:Azure dropping database support for MariaDB. Users advise...
by yawaramin on Monday October 02, 2023 @11:37AM
(#37739506)
If it's not going to be your problem in two years, then why would you complain about it?
Re:Azure dropping database support for MariaDB. Users advise...
by djoletina on Saturday September 30, 2023 @05:58PM
(#37720302)
I mean is it perfect? No. Are there better solutions and practices? Yes. But is it crazy and is it gonna cause irreparable damage? It is not unless you’re very irresponsible as a consumer. Either way that’s just my opinion.
Not giving updates and not allowing customers to create new instances is one thing, and is normally how these big deprecations are done. Outright destroying your customers' data just because they didn't migrate in time is wild (and its very easy for something like a database migration to take much longer than 2 years).