Need advice about which tool to choose?Ask the StackShare community!
Aerospike vs Cassandra: What are the differences?
Aerospike: Flash-optimized in-memory open source NoSQL database. Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees; 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.
Aerospike belongs to "In-Memory Databases" category of the tech stack, while Cassandra can be primarily classified under "Databases".
"Ram and/or ssd persistence " is the primary reason why developers consider Aerospike over the competitors, whereas "Distributed" was stated as the key factor in picking Cassandra.
Aerospike and Cassandra are both open source tools. Cassandra with 5.27K GitHub stars and 2.35K forks on GitHub appears to be more popular than Aerospike with 295 GitHub stars and 54 GitHub forks.
Uber Technologies, Facebook, and Spotify are some of the popular companies that use Cassandra, whereas Aerospike is used by JustWatch, Flyclops LLC, and StreetHawk. Cassandra has a broader approval, being mentioned in 342 company stacks & 240 developers stacks; compared to Aerospike, which is listed in 30 company stacks and 9 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.

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.

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.

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

i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
Pros of Aerospike
- Ram and/or ssd persistence16
- Easy clustering support12
- Easy setup5
- Acid4
- Scale3
- Performance better than Redis3
- Petabyte Scale3
- Ease of use2
Pros of Cassandra
- Distributed116
- High performance97
- High availability81
- Easy scalability74
- Replication52
- Reliable26
- Multi datacenter deployments26
- OLTP9
- Schema optional9
- Open source8
- Workload separation (via MDC)2
- Fast1
Sign up to add or upvote prosMake informed product decisions
Cons of Aerospike
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1