H2 Database

H2 Database

About TrustRadius ScoringScore 8.0 out of 100
H2 Database Engine

Overview

What is H2 Database?

H2 Database Engine is an open source, embeddable database management system (RDMS) written in Java.
Read more

Recent Reviews

For simplicity

8 out of 10
May 14, 2021
[H2 Database Engine is] being used for two different purposes. One is for running unit tests for application during compilation phase. …
Continue reading
Verified User
Employee
Read all reviews
Return to navigation

Product Details

What is H2 Database?

H2 Database Engine is an open source, embeddable database management system (RDMS) written in Java.

H2 Database Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (2)

Reviews

(1-2 of 2)
Popular Filters
Companies can't remove reviews or game the system. Here's why
June 03, 2021

H2 Database Engine is the in-memory database for your automated tests

Verified User
Employee in Information Technology
Computer Software Company, 1-10 employees
Score 8 out of 10
Vetted Review
Verified User
Use Cases and Deployment Scope
H2 Database Engine is primarily used for running application test cases by our development team. When changes are made to our codebase, we run automated test cases, and when the test case involves data manipulation, H2 Database Engine is used instead of a full blown database such as PostgreSQL. H2 Database Engine is lightweight, simple and runs in-memory, which makes it perfect for this use case.
Pros and Cons
  • 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.
  • There really is not a lot to say here as H2 Database Engine is not a general purpose database such as PostgreSQL or MySQL, so it has a niche use case for being an in-memory database, and it is very good at doing that. Perhaps one slight improvement would be some SQL queries that work with MySQL or PostgreSQL do not work with H2 Database Engine, and so if H2 Database Engine is used as an in-memory replacement for testing, that would create false negatives.
  • If H2 Database Engine can support some NoSQL databases, it would be fantastic.
Likelihood to Recommend
This really depends on the use case. For an in-memory replacement database for running unit test cases with, H2 Database Engine is an excellent option. However, if you are looking for a general purpose database for your production systems, then H2 Database Engine is not suited for this purpose.
May 14, 2021

For simplicity

Verified User
Employee in Information Technology
Computer Software Company, 1001-5000 employees
Score 8 out of 10
Vetted Review
Verified User
Use Cases and Deployment Scope
[H2 Database Engine is] being used for two different purposes. One is for running unit tests for application during compilation phase. This application runs is MySQL database normally, but for unit test purposes that is impractical. In compilation phase an in-memory H2 database is constructed and application tests are run against that. Another purpose is a small authentication security web-application that runs in a single instance. In this case some authentication related details are stored in H2 database that is stored to disk.
Pros and Cons
  • Simple setup, only needs a dependency added to application & few config lines.
  • Quick startup
  • Easy to use, existing code for MySQL works with H2 too
  • 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.
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.
Return to navigation