Cassandra vs Presto: What are the differences?
What is 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.
What is Presto? Distributed SQL Query Engine for Big Data. Presto is an open source distributed SQL query engine for running interactive analytic queries against data sources of all sizes ranging from gigabytes to petabytes.
Cassandra belongs to "Databases" category of the tech stack, while Presto can be primarily classified under "Big Data Tools".
"Distributed" is the top reason why over 96 developers like Cassandra, while over 9 developers mention "Works directly on files in s3 (no ETL)" as the leading cause for choosing Presto.
Cassandra and Presto are both open source tools. It seems that Presto with 9.22K GitHub stars and 3.12K forks on GitHub has more adoption than Cassandra with 5.23K GitHub stars and 2.33K GitHub forks.
According to the StackShare community, Cassandra has a broader approval, being mentioned in 337 company stacks & 230 developers stacks; compared to Presto, which is listed in 19 company stacks and 11 developer stacks.
What is Cassandra?
What is Presto?
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 Presto?
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