2020 LinuxQuestions.org Members Choice AwardsThis forum is for the 2020 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite projects/products of 2020. This is your chance to be heard! Voting ends on February 17th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For embedded systems, SQLite is hard to beat. If actual database servers are involved, PostgreSQL is the clear winner in terms of features, scalability, price (sorry Oracle) and performance. I'll choose PostgreSQL because it's what I use the most right now.
MariaDB has every feature the others wish they had and it actually scales, using a plethora of different replication technologies.
* Online schema changes! People always get stuffy about transactional DDL, but it's only for a single server. Where is that transaction running on a scaled solution?
* The columnstore is here for everyone as of 10.5. And now it can back onto bucket storage.
* Xpand/clustrix is still commercial, but it's actually horizonally scalable sql.
* Mariabackup! Learn it, use it, love it.
* You can have your JSON I guess...I prefer dynamic columns.
* Spider and Galera are immense. There are some huge installations of them both from hundres of terabytes per-cluster and beyond.
* InnoDB is now going through a big rewrite, because, you know, the InnoDB guys actually work at MariaDB. They have actually done well to poach a several engineers from the likes of sybase, ms, and ibm over the years. Maxscale didn't happen by accident!
Is this only for SQL databases? YottaDB has been doing a lot of interesting things this year and though it is not SQL itself it now has an SQL front-end, Octo since mid-September.
MariaDB has every feature the others wish they had and it actually scales, using a plethora of different replication technologies.
It also has the worst defaults of all databases I ever worked with, making it extremely hard to migrate existing databases from Windows to Linux or HP-UX.
It also has the worst possible user-management options, which makes me stay away from it as long as possible. dbeaver helps, but still.
MariaDB with it's complete solution of HA, Extreme OLTP Scale with Xpand engine, Extreme scale on the OLTP side with ColumnStore engine and MaxScale at the top to bring it all together in a beautiful and the most powerful package that makes it handle every typo of workload that one can throw at it!
I forgot to add that EnterpriseDB is missing from this list, which brings the horrid world of Oracle to be bearable on a PostgreSQL database with the addition of easy db-administration and better support. And it is waaaaaaay cheaper than Oracle.
EnterpriseDB essentially being PostgreSQL under the hood, I'm not asking to add it, but it might be worth adding it next year.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.