Percona Server for MongoDB vs. Titan Distributed Graph Database

It offers good support for the implementation of solutions in the public and on-premises cloud and integration with other services such as Hashicorp Vault for data encryption. One of the main advantages is the ease of configuration, in addition to offering transaction support for the different operations and scalability of the servers.

Incentivized

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.

Incentivized

• High performance
• Integration with other tools and services
• Big data projects oriented
• High availability and scalability

Incentivized

• Titan is really good for abstraction of underlying infrastructure. You can choose between different storage engine of your choice.
• Open source, backed by community, and free.
• Supports tinkerpop stack which is backed by apache.
• Uses gremlin for query language making the whole query structure standardized and open for extension if another graph database comes along in future.

Incentivized

• The learning curve makes it a bit tricky to use at first.
• Documentation is an aspect to improve, especially for people who are just starting out.
• At the interface level, the user experience could be improved.

Incentivized

• 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.
• Would love an official docker image.

Incentivized

One aspect to improve is the user experience since sometimes the steps to take are not clear and the user may need to review some of the actions before continuing with the next ones. Another aspect to improve is the documentation and support for developers who want to know the tool.

Incentivized

It offers good support for the implementation of solutions in the public and on-premises cloud and integration with other services such as Hashicorp Vault for data encryption. Also, it offers support for different compatible programming languages such as C, C ++, Java, as well as offering good support for the persistence of schema-free data and the possibility of saving data in memory.

Incentivized

At the performance level, it is similar to other solutions such as MongoDB and Percona Server for MySQL. and at the customization level, it offers better support for the development of specific solutions that seek good performance in transactions.

Incentivized

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.

Incentivized

• It offers a good alternative solution compared with other open source databases.
• We have many resources at the documentation level and other tools that help the integration with different programming languages.

Incentivized

• Steep learning curve. Your engineers would have to spend lots of time learning different components before they feel comfortable.
• Have to plan ahead. Maybe this is the nature of graph databases, but I found it difficult to change my schemas after I had data in production.
• It is free, so time is the only resource you have to put in titan.

Incentivized