Need advice about which tool to choose?Ask the StackShare community!
Cassandra vs Vertica: What are the differences?
Developers describe Cassandra as "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. On the other hand, Vertica is detailed as "Engineering experiences that amaze". Vertica provides a best-in-class, unified analytics platform that will forever be independent from underlying infrastructure.
Cassandra and Vertica belong to "Databases" category of the tech stack.
Cassandra is an open source tool with 5.34K GitHub stars and 2.36K GitHub forks. Here's a link to Cassandra's open source repository on GitHub.
Uber Technologies, Facebook, and Netflix are some of the popular companies that use Cassandra, whereas Vertica is used by Taboola, HomeUnion, and Points International. Cassandra has a broader approval, being mentioned in 431 company stacks & 1388 developers stacks; compared to Vertica, which is listed in 3 company stacks and 3 developer stacks.
The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.
The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.

Scylla can handle 1M/s events with a simple data model quite easily. The api to query is CQL, we have REST api but that's for control/monitoring

Cassandra is quite capable of the task, in a highly available way, given appropriate scaling of the system. Remember that updates are only inserts, and that efficient retrieval is only by key (which can be a complex key). Talking of keys, make sure that the keys are well distributed.

i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra

By 55M do you mean 55 million entity changes per 2 minutes? It is relatively high, means almost 460k per second. If I had to choose between Scylla or Cassandra, I would opt for Scylla as it is promising better performance for simple operations. However, maybe it would be worth to consider yet another alternative technology. Take into consideration required consistency, reliability and high availability and you may realize that there are more suitable once. Rest API should not be the main driver, because you can always develop the API yourself, if not supported by given technology.
Pros of Cassandra
- Distributed115
- High performance95
- High availability80
- Easy scalability74
- Replication52
- Multi datacenter deployments26
- Reliable26
- OLTP9
- Open source7
- Schema optional7
- Workload separation (via MDC)2
- Fast1
Pros of Vertica
- Shared nothing or shared everything architecture1
- Offers users the freedom to choose deployment mode1
- Flexible architecture suits nearly any project1
- End-to-End ML Workflow Support1
- All You Need for IoT, Clickstream or Geospatial1
- Freedom from Underlying Storage1
- Pre-Aggregation for Cubes (LAPS)1
- Automatic Data Marts (Flatten Tables)1
- Near-Real-Time Analytics in pure Column Store1
- Fully automated Database Designer tool1
- Query-Optimized Storage1
- Vertica is the only product which offers partition prun1
- Partition pruning and predicate push down on Parquet1
Sign up to add or upvote prosMake informed product decisions
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1