Need advice about which tool to choose?Ask the StackShare community!
Aerospike vs Scylla: What are the differences?
What is 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.
What is Scylla? Next Generation Cassandra. Real-time big data database, with scale-up performance of 1,000,000 IOPS per node, scale-out to 100s of nodes and 99 latency of less than 1 msec.
Aerospike can be classified as a tool in the "In-Memory Databases" category, while Scylla is grouped under "Databases".
Aerospike and Scylla are both open source tools. Scylla with 5.25K GitHub stars and 619 forks on GitHub appears to be more popular than Aerospike with 307 GitHub stars and 57 GitHub forks.
According to the StackShare community, Aerospike has a broader approval, being mentioned in 38 company stacks & 36 developers stacks; compared to Scylla, which is listed in 16 company stacks and 6 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.
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.
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.
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
The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:
We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.
Pros of Aerospike
- Ram and/or ssd persistence16
- Easy clustering support12
- Easy setup5
- Performance better than Redis3
- Petabyte Scale3
- Ease of use2
Pros of ScyllaDB
- Fewer nodes1
- Scale up1
- High availability1
- Written in C++1
- High performance1