MariaDB vs Universal Data Access Components: Which is a better fit?

Speaker 1: I'm Justin, a DevOps engineer, and I give MariaDB four out of five stars. For more reviews like these, please click the link below. Before MariaDB, we had MySQL. Like a lot of companies, we use MySQL because it worked, it was relatively easy to use and it was open source and then Oracle bought it out and we are very familiar with Oracle and wanted nothing to do with any Oracle backed product. We chose MariaDB because we wanted something that was like MySQL, sort of a drop-in replacement with a lot of the same features and better community stewardship. We did not want to have another open-source project that would get swallowed up by a company like Oracle. It was very, very simple getting started with MariaDB, essentially every library and program we had to work with MySQL also worked with MariaDB. So it was just applying the same MySQL knowledge we already had to a different context. If you're thinking about MariaDB, two things, the first thing is MariaDB and MySQL have diverged a little bit more since I know initially adopted it. They are having some compatibility issues and I expect that to get a little bit worse over time. So think carefully about whether your existing MySQL tooling will in fact work with MariaDB. It's no longer necessarily a drop-in replacement. The second thing is MariaDB just announced a new release cadence, essentially before, they would have an annual release that will be supported for about, I think, five years. Now, they're releasing new updates every quarter and they're each going to be supported for one year. So, if you like the idea of more frequent updates, then you'll love MarieDB's new cadence. If not, then you may wish to consider something that's roughly equivalent that has a longer support cycle like PostgreSQL.