[arrakeenrevived]

In comparison to other cloud companies, AWS "deprecated" SimpleDB over a decade ago and stopped letting new people use it, but still hasn't deleted the data for anyone that is still using it. EC2 Classic was the same.

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).

[alwaysrunning]

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.

[mpixel]

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.

[yawaramin]

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?

[amtamt]

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.

[yawaramin]

If it's not going to be your problem in two years, then why would you complain about it?

[djoletina]

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.