QuestDB is an open source time series database. It implements SQL and exposes a Postgres wire protocol, a REST API, and supports ingestion with InfluxDB line protocol.
N/A
Titan
Score 8.0 out of 10
N/A
Titan is an open-source distributed graph database developed by Aurelius. Aurelius is now part of Datastax (since February 2015).
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.
Titan is definitely a good choice, but it has its learning curve. The documentation may lack in places, and you might have to muster answers from different sources and technologies. But at its core, it does the job of storing and querying graph databases really well. Remember that titan itself is not the whole component, but utilizes other technologies like cassandra, gremlin, tinkerpop, etc to do many other things, and each of them has a learning curve. I would recommend titan for a team, but not for a single person. For single developer, go with Neo4j.
The community is lacking deep documentation. I had to spend many nights trying to figure many things on my own. As graph databases will grow popular, I am sure this will be improved.
Not enough community support. Even in SO you might not find many questions. Though there are some users in SO who quickly answer graph database questions. Need more support.
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.
To be honest, titan is not as popular as Neo4j, though they do the same thing. In my personal opinion, titan has lot of potential, but Neo4j is easier to use. If the organization is big enough, it might choose titan because of its open source nature, and high scalability, but Neo4j comes with a lot of enterprise and community support, better query, better documentation, better instructions, and is also backed by leading tech companies. But titan is very strong when you consider standards. Titan follows gremlin and tinkerpop, both of which will be huge in future as more graph database vendors join the market. If things go really well, maybe Neo4j might have to support gremlin as well.
