MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.
N/A
MySQL
Score 8.0 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
We migrated away from MySQL because of stability issues; when choosing a new database system we considered FirebirdSQL (having some experience from other projects) and did not use it because of stability and lack of standard SQL features in its query language; and Amazon's …
We selected MariaDB over MySQL because of their true open source model and performance optimizations. It was also helpful that it is a drop-in replacement for MySQL so there was no need to update our various software drivers.
Thanks to MySQL compatibility, everything you've learned while using it can be utilized when using MariaDB. Therefore it's a better choice than MongoDB and MSSQL if you're looking to switch away from MySQL. MariaDB is also a very mature and stable product, unlike MongoDB that …
MariaDB provided the best fit for our business in upgrading legacy systems which were originally designed to use MySQL as a backend. By using MariaDB, no changes to the overall systems needed to be altered, reducing the time needed to upgrade everything. Other solutions …
MySQL is still a great solution, but MariaDB offers a more extensive set of free features than are available for MySQL. We also feel more confident that MariaDB will remain free to use over time. End users haven't noticed much of a difference, but from a development cost …
We tried Percona also, but we sometimes having trouble with it and on some cases it having lesser performance than MariaDB. MySQL is the the facto standard, we use this only in scenario that it cannot be replaced by MariaDB. MSSQL is used only if the client ask for Windows …
MariaDB is very similar to MySQL, but MariaDB has more alternative database engines and ideas for the future where MySQL is offers the stable and more mature version (if not stale).
MariaDB is perhaps the best open source database server available, combining a wide range of supported platforms, MySQL compatibility, a low footprint, and reasonably high performance. If you have cost constraints, or limited server resources, I recommend MariaDB, particularly …
MariaDB is the clear winner compared to any other database I've used. Reliable, scale-able, affordable--you name the consideration and MariaDB is the winner.
MariaDB is cheaper than Oracle Database and MSSQL server. MySQL owned by Oracle. So MariaDB has too many forks, but enough people in the community. PostgreSQL has a larger community and better administration. However, it s not like MariaDB w/ Galera. MariaDB is not good for …
MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects …
Although big players in the market such as Red Hat Enterprise Linux and Fedora jumped ship to use MariaDB, we found it more viable to use MySQL as a company. This was because MySQL was open source and offered a lot more functionality than other same priced software that were …
The three are relational databases or managers for relational database (except for MariaDB whose approach is based on NoSQL models) with the ability to store large databases and respond to demanding business circumstances, however MySQL compared to Microsoft SQL Server …
I'm not that expert on MariaDB, but as far as I know, it has great support from tools and frameworks, but it's not that usual to find hosting with it installed rather than MySQL. Since MariaDB is a 'fork' from MySQL (since it was bought by Oracle), the transition from MySQL is …
After Oracle bought MySQL, I have pivoted some projects to use MariaDB instead, which is a fork of MySQL and maintained by the community and original developers of MySQL. This is free under the GNU GPL, and is not impacted by decisions Oracle makes for MySQL. RDS has the …
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost …
A bit on the more complex side, but definitely one of the more popular solutions between our customers. As a stable alternative to the sometimes really pricy Oracle DB, it performed well for most of our not-database-heavy projects. It was a bit slower than no-SQL solutions on …
It is one of the tools that we had stopped using some time ago and in the last year we amplified its use thanks to its benefits and new functionalities.
Of course compare to no SQL databases it's slower but there is a completely different use case for them... In my opinion it is better than PostgreSQL, it's easier to configure and has the same performance, or approximately the same. Of course Oracle Database is a way bigger …
We had been using indexes on our MySQL databases for a while now but never before properly learned about them. Generally I put an index on any fields that I will be searching or selecting using a WHERE clause but sometimes it doesn't seem so black and white.
I prefer MySQL because of the simplicity of getting started and the ease of use. It has a very simple to use editor where one is able to input their SQL code and execute it from in application.
MySQL provides a feature to easily move to another technology. As we know, most of the users like to use MySQL in the backend because it reduces the overall business cost. No need to pay additional charges. Regularly updated.
The main argument of this decision was by popularity. At the time (2010), MySQL was the most popular open source database. Between 2010 and today, we evaluated different databases and PostgreSQL is a great competitor. SQL Server is good for windows applications but it's not …
I have used more than 10 different SQL databases over the course of my career. Of those, the three I find myself using over and over include MySQL, Oracle and SQL Server. I have actually replaced smaller deployments of Oracle and SQL Server with MySQL as a way to reduce …
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.
Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
We have launched several inquiries to MariaDB support and they have always responded very quickly and have not been tutoring for the duration of the incident/problem.
Likewise, they want to hold constant meetings with the client to get their opinion as well as how they can help.
I see a very human support and concerned about the customer.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects on the same environment with little overhead. One of the best features that MariaDB has is the ability of backup or dump data to standard text sql statements. That was one of the reasons why we choose MariaDb because it makes backups or transferring data a snap
MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.