Likelihood to Recommend For running application tests it's well suited. H2 [Database Engine] can replace the real-world database solution for them easily and removes the requirement to set up a a separate database instance just for running unit tests. For using in actual production application one needs to consider scale. H2 is suitable if application runs in single instance and database is located in same machine as a file where that application runs. This means the application shouldn't have a large user base. However it's easy to switch to an actual
MySQL instance if the need arises, it's most likely only a configuration change and doesn't require new code.
Read full review From my own perspective and the tasks that I perform on a daily basis, MySQL is perfect. It has a reasonable footprint, is fast enough and offers the security and flexibility I need. Everyone has their preferred applications and, no doubt, for larger data warehouses or more intensive applications, MySQL may have its limits, but for the area that I operate in, it's a great match.
Read full review Pros Can run as an in-memory database. Simple and quick to get started with, and is light weight (only 2MB). SQL compliant so it compatible with most relational databases. Read full review Security: is embedded at each level in MySQL. Authentication mechanisms are in place for configuring user access and even service account access to applications. MySQL is secure enough under the hood to store your sensitive information. Also, additional plugins are available that sit on top of MySQL for even tighter security. Widely adopted: MySQL is used across the industry and is trusted the most. Therefore, if you face any problems, simply Google it and you shall land in plenty of forums. This is a great relief as when you are in a need of help, you can find it right in your browser. Lightweight application: MySQL is not a heavy application. However, the data you store in the database can get heavy with time, but as in the configuration and MySql application files, those are not very heavy and can easily be installed on legacy systems as well. Read full review Cons There's a warning in official FAQ "Is it Reliable?"-section which makes it seem like H2 is not yet a mature product. If raw SQL queries are used there maybe be differences between MySQL & H2. ORM library should be used. Support seems to be community-based only. Read full review Although you can add the data you require as more and more data is added, the fixity of it becomes more critical. As the demand, size, and use of the system increase, you may also need to change or acquire more equipment on your servers, although this is an internal inconvenience for the company. Read full review Likelihood to Renew 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.
Read full review Usability 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.
Read full review Support Rating The support staff is friendly, knowledgeable, and efficient. I only had to get part way through my explanations before they had a solution. They will walk you through a fix or actually connect in and fix the problem for you--or would if you can allow it. I've done it both ways with them. They are always forthcoming with 'how to do this if it happens again' information. I love working with MySQL support.
Read full review Implementation Rating 1. Estimate your data size. 2. Test, test, and test.
Read full review Alternatives Considered While both can run as an in-memory database, H2 Database Engine was just so much easier for us to use since we primarily use the Java stack and H2 Database Engine is also built with Java.
Read full review 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.
Read full review Return on Investment Doesn't take time from developers, once it's configs are set up for testing it works in everyone's development environments Easy to integrate in application, no need to setup separate database software, no maintenance No need to deal with infrastructure related issues/costs - database runs in same machine as the application that uses it. Read full review As it is an open source solution through community solution, we can use it in a multitude of projects without cost license The acquisition by Oracle makes you need to contract support for the enterprise version If you have knowledge about oracle databases, you can get more out of the enterprise version Read full review ScreenShots