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 QuestDB is well suited for any use case where you need to store large amount of data and the performance is the key factor - for both reads and writes. So use cases like market data storage in financial industry, any kind of telemetry, etc.
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 Extreme performance. Super easy to use. Compatibility with Influx line protocol. PostgreSQL compatibility. Out of order timestamps. Support for multiple records with same timestamp. Integration with Grafana. Team responsiveness. 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 New project so needs a bit polishing. 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 We were looking for time series database that will be able to handle L2 market data and came across QuestDB. From the beginning we were impressed how well the QuestDB performs and that it actually significantly outperforms all other open source TSDB on market like
InfluxDB ,
ClickHouse ,
Timescale , etc. Apart from the excellent performance it is also super easy to use and deploy which makes the experience of using the database very pleasant - we were able to be up and running and storing data within few hours. Topic itself is the QuestDB team that is super responsive on their slack channel and always ready to help with any query. They are constantly improving the product and if there is some missing feature that is blocking you from usage they always try the best to implement such feature asap and release a new version - one of the best support I have ever seen so far in open source community.
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 Reduced cost. Increased efficiency. Faster time to market. Read full review ScreenShots