Redis vs Rockset

Choosing the right database is a critical choice when building any software application. All databases have different strengths and weaknesses when it comes to performance, so deciding which database has the most benefits and the most minor downsides for your specific use case and data model is an important decision. Below you will find an overview of the key concepts, architecture, features, use cases, and pricing models of Redis and Rockset so you can quickly see how they compare against each other.

The primary purpose of this article is to compare how Redis and Rockset perform for workloads involving time series data, not for all possible use cases. Time series data typically presents a unique challenge in terms of database performance. This is due to the high volume of data being written and the query patterns to access that data. This article doesn’t intend to make the case for which database is better; it simply provides an overview of each database so you can make an informed decision.

Redis Overview

Redis, which stands for Remote Dictionary Server, is an open-source, in-memory data structure store that can be used as a database, cache, and message broker. It was created by Salvatore Sanfilippo in 2009 and has since gained significant popularity due to its high performance and flexibility. Redis supports various data structures, such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, and geospatial indexes with radius queries.

Rockset Overview

Rockset is a real-time indexing database designed for fast, efficient querying of structured and semi-structured data. Founded in 2016 by former Facebook engineers, Rockset aims to provide a serverless search and analytics solution that enables users to build powerful applications and data-driven products without the complexities of traditional database management.

Redis for Time Series Data

Redis has a dedicated module for working with time series data called RedisTimeSeries. RedisTimeSeries offers functionality like downsampling, data retention policies, and specialized queries for time series data in Redis. Being an in-memory database, Redis will be very fast for reading and writing time series data, but due to the cost of RAM compared to disk using Redis could become expensive depending on the size of your dataset. If your use case doesn’t require extremely fast response times, you could save money by going with a more traditional time series database.

Rockset for Time Series Data

Rockset’s real-time indexing and low-latency querying capabilities make it an excellent choice for time series data analysis. Its schemaless ingestion and support for complex data types enable effortless handling of time series data, while its Converged Index ensures efficient querying of both historical and real-time data. Rockset is particularly suitable for applications that demand real-time analytics, such as IoT monitoring and anomaly detection.

Redis Key Concepts

• In-memory store: Redis stores data in memory, which allows for faster data access and manipulation compared to disk-based databases .
• Data structures: Redis supports a wide range of data structures, including strings, hashes, lists, sets, and more, which provide flexibility in how data is modeled and stored.
• Persistence: Redis offers optional data persistence, allowing data to be periodically saved to disk or written to a log for durability.
• Pub/Sub: Redis provides a publish/subscribe messaging system, enabling real-time communication between clients without the need for a centralized message broker.

Rockset Key Concepts

• Converged Index: Rockset uses a unique indexing approach that combines both an inverted index and a columnar index, allowing the database to optimize for both search and analytics use cases.
• Schemaless Ingestion: Rockset automatically infers schema on ingestion, making it easy to work with semi-structured data formats like JSON.
• Virtual Instances: Rockset uses the concept of virtual instances to provide isolation and resource allocation to different workloads, ensuring predictable performance.

Redis Architecture

Redis is a NoSQL database that uses a key-value data model, where each key is associated with a value stored as one of Redis’ supported data structures. The database is single-threaded, which simplifies its internal architecture and reduces contention. Redis can be deployed as a standalone server, a cluster, or a master-replica setup for scalability and high availability. The Redis Cluster mode automatically shards data across multiple nodes, providing data partitioning and fault tolerance.

Rockset Architecture

Rockset uses a cloud-native, serverless architecture that is built on top of a distributed, shared-nothing system. It is a NoSQL database, which allows for greater flexibility and scalability compared to traditional relational databases. The core components of Rockset’s architecture include the Ingestion Service, Storage Service, and Query Service. The Ingestion Service is responsible for ingesting data from various sources, while the Storage Service maintains the Converged Index. The Query Service processes queries and provides APIs for developers to interact with the database.