SAP Adaptive Server Enterprise (ASE) vs. Titan Distributed Graph Database

We use this for an inbuilt security management system, where it performs well in a scaled setup with a large volume of live data with high availability. Also, the performance is up to the mark for the large statement flow. From a DBA perspective, a lot of parameters need to be fine-tuned for the specific environment needs, which can cause overhead. Expertise is limited, and the learning curve is steep for the SAP ASE.

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 availability and reliability.
• High performance.
• Monitoring of threshold based events.
• Security at multiple levels.
• Query plan optimization.
• Lock management.
• Access to HANA.

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

• A quick button for devs to switch instances into a dev mode (eliminating logs, and such).
• Licensing is far too complicated. Simplify pricing.

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

Our licenses are perpetual. It is the support that we will be renewing. We will renew because we continue to use and receive value from the product.

Incentivized

Well-suited in the security domain, high performance, and low latency of the DBMS. In terms of the DBA perspective, a dedicated monitoring tool (Cockpit) helps a lot in terms of managing the database, which helps in identifying bottlenecks during performance issues. Also, it helps us to send custom alerts related to Database activities.

Incentivized

Incredibly responsive, saving us countless hours in troubleshooting.

Incentivized

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

• Positive ROI.
• Ease of use with minimal training required to write high performance SQL (assumes a knowledge of SQL already).
• Ease of database administration.
• Sometimes upgrades can be difficult.
• Changing platforms can be difficult (changing say from SPARC to Intel).
• Changing operating systems can be difficult (changing from Solaris to linux).

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