Hi All, We are currently in the process of building statistical analysis system. As a part of technology evaluation and due diligence we are drawing a comparison between Titan-Cassandra combination vs OrientDB.
There was a topic in these forums that compared Cassandra and OrientDB (last update in October 2012). The comparison was quite succinct within the applicable context and the points therein have been factored in as a part of the due diligence. The biggest difference is obviously the fact that the comparison was between a columnar DB and a graph DB. The inclusion of Titan into this discussion makes it apples to apples comparison. Besides, a lot has changed between October 2012 and January 2014 for OrientDB (Hazelcast support, Multi-master support etc) Following is a high level summary of the scale requirements and internal design consensus we have: 1. 500-750 billion live samples per year (at this point in time we do not have visibility if all this will necessarily translate into vertices per se). 2. A federated model/system is acceptable 3. Over and above the 500-750 billion live sample, the application will have a couple of million records (just in case an additional drop created chaos in the ocean :) ) Given that we can store JSON data in Cassandra (with the knowledge that marshalling and umarshalling will induce latency) and Titan can provide graph relationship, what, in the estimation of this community tips the scales in favor of OrientDB. At the time of this writing, I have only managed to scratch the surface and I am relatively new to NoSQL and Big Data systems in general. So, if the question lacks clarity/depth, please let me know and I will share any additional information required Thanks LSP PS - Wishing you all a happy new year and a great 2014. -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
