For those who, like me, were looking at the master branch and assumed the codebase was inactive, this is apparently the branch where development is happening:<p><a href="https://github.com/thinkaurelius/titan/tree/titan09" rel="nofollow">https://github.com/thinkaurelius/titan/tree/titan09</a><p>This is version 0.9, and they are gearing up for a 1.0 release.<p>Anyone here using it who can summarize their experience? Production-readiness, performance, general usability as an alternative to other NoSQL databases?
As another commentator mentioned, <a href="http://orientDB.com/" rel="nofollow">http://orientDB.com/</a> looks interesting as well.<p>Those complaining about Titan being abandoned, don't worry. Getting better graph features into the Cassandra family is one of the best things they could do. So consider this a win-win.<p>For those looking for a javascript variant, check out my project <a href="http://gunDB.io/" rel="nofollow">http://gunDB.io/</a> which is a browser based graph database. Definitely not as "academic" leaning as Titan, but it is more friendly towards web developers which Titan is not.
I need a distributed, scalable solution for querying set intersections. Before rolling my own I may give this a chance, though Apache accumulo looks like the first option.
I suppose it's a difference in terminology, but it seems strange for them to state:<p>> Support for ACID and eventual consistency.<p>As ACID typically implies strong consistency. To quote the wikipedia page on eventual consistency that they link to:<p>> Eventually consistent services are often classified as providing BASE (Basically Available, Soft state, Eventual consistency) semantics, in contrast to traditional ACID (Atomicity, Consistency, Isolation, Durability) guarantees.
another very interesting project
<a href="http://orientdb.com/orientdb/" rel="nofollow">http://orientdb.com/orientdb/</a>