Need advice about which tool to choose?Ask the StackShare community!
Redis vs Scylla: What are the differences?
- Key Difference 1: Data Structure: Redis is a key-value store that offers various data structures such as strings, lists, sets, sorted sets, etc., making it highly flexible for different use cases. On the other hand, Scylla is a highly scalable NoSQL database that is built upon Apache Cassandra and focuses on providing wide column store functionality. It organizes data into tables with a defined schema, allowing for efficient querying and storage of large datasets.
- Key Difference 2: Data Distribution: Redis utilizes a master-slave replication model, where multiple slave nodes can replicate data from a single master node. This provides high availability and read scalability but limits write scalability. In contrast, Scylla follows a masterless distributed architecture using consistent hashing and gossip protocols. It allows for automatic partitioning and distribution of data across multiple nodes, ensuring high write and read scalability.
- Key Difference 3: Durability: Redis offers durability through a combination of techniques such as point-in-time snapshots, append-only files, and asynchronous replication. However, it is optimized for in-memory operations and may not be as suitable for scenarios with large datasets or high write frequencies. Scylla, on the other hand, is designed for durability, supporting both in-memory and on-disk storage. It integrates with distributed file systems and provides configurable levels of data persistence to meet various durability requirements.
- Key Difference 4: Consistency Models: Redis supports multiple consistency models, including eventual consistency and strong consistency, depending on the data structure used. It allows applications to choose the level of consistency required for their use case. Scylla follows a tunable consistency model, giving developers the ability to define their desired consistency level on a per-operation basis. This flexibility allows for a trade-off between consistency, availability, and partition tolerance.
- Key Difference 5: Query Language: Redis uses a simple query language that operates directly on its data structures. It supports a set of commands and pipelines, making it easy to manipulate and retrieve data. Scylla, being a wide column store, utilizes the CQL (Cassandra Query Language) which is similar to SQL but adapted for use in NoSQL databases. CQL provides powerful querying capabilities with support for filtering, data aggregation, and secondary indexes.
- Key Difference 6: Performance and Scaling: Redis is known for its exceptional performance as an in-memory database. It can handle high volumes of operations with low latencies. However, when it comes to scaling beyond the capacity of a single node, Redis requires additional sharding and partitioning mechanisms. Scylla, being designed for horizontal scalability from the ground up, performs exceptionally well at massive scales. It efficiently utilizes hardware resources across a cluster of nodes, making it ideal for high-performance and high-throughput applications.
In Summary, Redis and Scylla differ in terms of their data structure flexibility, data distribution models, durability options, consistency models, query languages, and performance/scaling capabilities.
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.
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 Redis
- Performance886
- Super fast542
- Ease of use513
- In-memory cache444
- Advanced key-value cache324
- Open source194
- Easy to deploy182
- Stable164
- Free155
- Fast121
- High-Performance42
- High Availability40
- Data Structures35
- Very Scalable32
- Replication24
- Great community22
- Pub/Sub22
- "NoSQL" key-value data store19
- Hashes16
- Sets13
- Sorted Sets11
- NoSQL10
- Lists10
- Async replication9
- BSD licensed9
- Bitmaps8
- Integrates super easy with Sidekiq for Rails background8
- Keys with a limited time-to-live7
- Open Source7
- Lua scripting6
- Strings6
- Awesomeness for Free5
- Hyperloglogs5
- Transactions4
- Outstanding performance4
- Runs server side LUA4
- LRU eviction of keys4
- Feature Rich4
- Written in ANSI C4
- Networked4
- Data structure server3
- Performance & ease of use3
- Dont save data if no subscribers are found2
- Automatic failover2
- Easy to use2
- Temporarily kept on disk2
- Scalable2
- Existing Laravel Integration2
- Channels concept2
- Object [key/value] size each 500 MB2
- Simple2
Pros of ScyllaDB
- Replication2
- Fewer nodes1
- Distributed1
- Scale up1
- High availability1
- Written in C++1
- High performance1
Sign up to add or upvote prosMake informed product decisions
Cons of Redis
- Cannot query objects directly15
- No secondary indexes for non-numeric data types3
- No WAL1