Following the acquisition of Aurelius by DataStax, and since Titan 1.0.0 was released in September 2015 and received very few commits since then, I wonder whether it is safe to use TitanDB in production. Can anyone please give some insight?
We are running a Titan graph, on top of HBase, with about 30TBs of data, and a lot of features are missing.
For example, a must-have is the ability to perform OLAP operations on the graph, such as deleting redundant vertices using Spark.
Although it seems like Tinkerpop is going that way using its SparkGraphComputer, it does not work well - the implementations of reading data from HBase using Hadoop InputFormat is buggy, and a lot of scenarios are not handled (for example, a vertex that is connected to itself in a loop makes the code raise an exception and terminate). In addition, the efficiency of the sections that parse vertices from raw data is just bad - a lot of buffer allocations that are redundant and make everything slow.
If you are planning on a big graph for the long term, I don't think Titan is suitable - unless you are going to contibute code by your own.