InfluxDB vs. QuestDB vs. RaimaDB

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

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.

Works very well in applications designed for IoT devices where performance and footprint are of great importance.

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• 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.

• First of all the performance of RDM was superior compared to SQLite in my multi-user environment (about 200 users). The pricing was surprisingly good compared to other high-performance databases.
• Decreased time to market, a faster and more performant application overall and lower maintenance costs.
• They run on most RTOS and can be used in a cross-platform environment.

• GUI based administrator console

Incentivized

• New project so needs a bit polishing.

• I would like to see REST API with a GUI for administration

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

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.

RDM performs way better than SQLite when the database is larger and has multiple users.

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

• Reduced cost.
• Increased efficiency.
• Faster time to market.

• Decreased time to market
• Decreased maintenance and service costs on hardware.