Oracle's icy touch. It was foretold. :D
I'm not going to stop using it because it's not "true open source." I'm going to stop using it because there's better databases out there.
The author is right that usage is dropping, but that really has no bearing on whether or not it is open source. Technologies get replaced all the time regardless of the license they use.
Author is also being careful with the DB-Engines screen shot, usage of MySQL may be dropping, but it's still number two (below Oracle, above MSSQL - which shows the same curve, above Postgres, far above MariaDB and SQLite) https://db-engines.com/en/ranking_trend
From my experience MariaDB is not necessarily better than MySQL. The 8.x line brought many interesting features. I dream on switch to Postgres, and try every year but for my use case MySQL is still superior (100Bi+ rows for large texts, and heavy modified - I´m also space constrained - So I need data compression and the VACUUM are not good.)
The percona distribution is very good!
The storage engine is one of postgres's weakest points. I hope OrioleDB will eventually give us a more robust and easier to use replacement.
If space constrained and wanting compression, why not do that at the filesystem or block layer if it's not supported in the app?
I'm stuck on MySQL because converting to postgres is hard, the tool everyone recommends (pgloader) doesn't work with current MySQL (https://github.com/dimitri/pgloader/issues/782), anyone know another way?
It does work, I just used pgloader to migrate a 16 GB database from MySQL 8.4 to PostgreSQL 18 last week (around 700 tables). It's not big, but their problems seem to be with authentication, not database size or functionality.
Have you tried it doing it yourself?
How big of a DB are we talking about? You might need to recreate the whole DB schema / structure manually from scratch in PostgreSQL and then dump the data and load it in PG via standard SQL file exports in the correct table order to avoid failures due to FK constraints. This is a gross oversimplification but you get the gist
In fact I don't get the gist :) but thanks for your reply. All I know about databases is following instructions to set one up as part of a LAMP/FAMP installation.
Happily using MariaDB (as packaged with Debian) in production here...
I used MariaDB in Azure, but got notified it was retired. Anyway, migrated to sqlite.
I would argue that the reason to stop using it is that is a pretty bad piece of software to begin with, not because it's not "true open source" but hey, whatever floats your boat, right?
Who's still using MySQL on the back end? Most Linux distributions come with MariaDB. Is it Windows servers?
I'm pretty sure Facebook is still running it. They've done a migration to 8.0 a couple of years after it came out (it was a massive release).
MySQL performs well at large scale, and has a very cool and weird storage engine option called MyRocks, that slows read performance but allows demented write rates and compression.
But yes, it is very bad.