Cassandra vs TokuMX: What are the differences?
Cassandra: A partitioned row store. Rows are organized into tables with a required primary key. Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL; TokuMX: A high-performance, concurrent, compressing, drop-in replacement engine for MongoDB. TokuMX is a drop-in replacement for MongoDB, and offers 20X performance improvements, 90% reduction in database size, and support for ACID transactions with MVCC. TokuMX has the same binaries, supports the same drivers, data model, and features of MongoDB, because it shares much of its code with MongoDB.
Cassandra and TokuMX can be categorized as "Databases" tools.
"Distributed" is the primary reason why developers consider Cassandra over the competitors, whereas "When your two-week MongoDB love affair ends, try this" was stated as the key factor in picking TokuMX.
Cassandra and TokuMX are both open source tools. Cassandra with 5.27K GitHub stars and 2.35K forks on GitHub appears to be more popular than TokuMX with 679 GitHub stars and 90 GitHub forks.
What is Cassandra?
What is TokuMX?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Cassandra?
What are the cons of using TokuMX?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Stitch is a wrapper around a Cassandra database. It has a web application that provides read-access to the counts through an HTTP API. The counts are written to Cassandra in two distinct ways, and it's possible to use either or both of them:
Real-time: For real-time updates, Stitch has a processor application that handles a stream of events coming from a broker and increments the appropriate counts in Cassandra.
Batch: The batch part is a MapReduce job running on Hadoop that reads event logs, calculates the overall totals, and bulk loads this into Cassandra.
Cassandra is our data management workhorse. It handles all our key-value services, supports time-series data storage and retrieval, securely stores all our audit trails, and backs our Datomic database.
While we experimented with Cassandra in the past, we are no longer using it. It is, however, open for consideration in future projects.
We are using Cassandra in a few of our apps. One of them is as a count service application to track the number of shares, clicks.. etc