The project was developed and maintained by Salvatore Sanfilippo, starting in 2009.[23] From 2015 until 2020, he led a project core team sponsored by Redis Labs.[24] Salvatore Sanfilippo left Redis as the maintainer in 2020.[25] In 2021 Redis Labs dropped the Labs from its name and now is known simply as "Redis".[26]
In 2018, some modules for Redis adopted the SSPL.[27] In 2024, the main Redis code switched to dual-licensed under the Redis Source Available License v2 and the Server Side Public License v1.[6]
History
Salvatore Sanfilippo, the original developer of Redis (photo taken in 2015)
The name Redis means Remote Dictionary Server.[7] The Redis project began when Salvatore Sanfilippo, nicknamed antirez, the original developer of Redis, was trying to improve the scalability of his Italian startup, developing a real-time web log analyzer. After encountering significant problems in scaling some types of workloads using traditional database systems, Sanfilippo began in 2009 to prototype a first proof of concept version of Redis in Tcl.[28] Later Sanfilippo translated that prototype to the C language and implemented the first data type, the list. After a few weeks of using the project internally with success, Sanfilippo decided to open source it, announcing the project on Hacker News. The project began to get traction, particularly among the Ruby community, with GitHub and Instagram being among the first companies adopting it.[29][30]
In June 2015, development became sponsored by Redis Labs.[35]
In August 2018, Redis Labs announced the switch to a source-available software license, Server Side Public License for some of the optional modules available for Redis,[27] while affirming that the core software will remain BSD-licensed.[36]
In October 2018, Redis 5.0 was released, introducing Redis Stream – a new data structure that allows storage of multiple fields and string values with an automatic, time-based sequence at a single key.[37]
In June 2020, Salvatore Sanfilippo stepped down as Redis' sole maintainer. Sanfilippo was succeeded by Yossi Gottlieb and Oran Agra.[38][39]
In March 2024, Redis switched to a different proprietary software license, styled as the Redis Source Available License v2, and the Server Side Public License v1, also for its core repository,[6] breaking the 2018 pledge. As a consequence, the Linux Foundation created a fork under the name of Valkey,[40] allowing community maintainers, contributors, and users to continue working on an open source version of the Redis database.
Differences from other database systems
Redis popularized the idea of a system that can be considered a store and a cache at the same time. It was designed so that data is always modified and read from the main computer memory, but also stored on disk in a format that is unsuitable for random data access. The formatted data is only reconstructed into memory once the system restarts.
Redis also provides a data model that is very unusual compared to a relational database management system (RDBMS). User commands do not describe a query to be executed by the database engine but rather specific operations that are performed on given abstract data types. Therefore data must be stored in a way which is suitable later for fast retrieval. The retrieval is done without help from the database system in form of secondary indexes, aggregations or other common features of traditional RDBMS. The Redis implementation makes heavy use of the fork system call, to duplicate the process holding the data, so that the parent process continues to serve clients while the child process writes the in-memory data to disk.
Popularity
According to monthly DB-Engines rankings, Redis is often the most popular key–value database.[10] Redis has also been ranked the #4 NoSQL database in user satisfaction and market presence based on user reviews,[41] the most popular NoSQL database in containers,[42] and the #4 Data store of 2019 by ranking website stackshare.io.[43] It was voted most loved database in the Stack OverflowDeveloper Survey each year from 2017 to 2021.[44]
Supported languages
Since version 2.6, Redis features server-side scripting in the language Lua.[45]
Redis maps keys to types of values. An important difference between Redis and other structured storage systems is that Redis supports not only strings, but also abstract data types:
HyperLogLogs used for approximated set cardinality size estimation, available since Redis 2.8.9 in April 2014.[37]
Stream of entries with consumer groups, allows you to store multiple fields and string values with an automatic, time-based sequence at a single key, available since Redis 5.0 in October 2018[37]
Geospatial data through the implementation of the geohash technique, available since Redis 3.2.[49]
The type of a value determines what operations (called commands) are available for the value. Redis supports high-level, atomic, server-side operations like intersection, union, and difference between sets and sorting of lists, sets and sorted sets.
More data types are supported based on Redis Modules API. Note, that some of them are dual licensed, and not under the BSD 3 clause:[50]
JSON – RedisJSON[51] implements ECMA-404 (the JavaScript Object Notation Data Interchange Standard) as a native data type.[52]
Search - A query engine for Redis, providing secondary indexing, full-text search, vector similarity search and aggregations.[53]
Time series – RedisTimeSeries[54] implements a time series data structure
Graph – RedisGraph[57] implements a queryable property graph
RedisGraph has been discontinued,[58] and continued in the form of a fork called FalkorDB.[59]
Persistence
Redis typically holds the whole dataset in memory. Versions up to 2.4 could be configured to use what they refer to as virtual memory[60] in which some of the dataset is stored on disk, but this feature is deprecated. Persistence in Redis can be achieved through two different methods. First by snapshotting, where the dataset is asynchronously transferred from memory to disk at regular intervals as a binary dump, using the Redis RDB Dump File Format. Alternatively by journaling, where a record of each operation that modifies the dataset is added to an append-only file (AOF) in a background process. Redis can rewrite the append-only file in the background to avoid an indefinite growth of the journal. Journaling was introduced in version 1.1 and is generally considered the safer approach.
By default, Redis writes data to a file system at least every 2 seconds, with more or less robust options available if needed. In the case of a complete system failure on default settings, only a few seconds of data would be lost.
Replication
Redis supports master–replica replication. Data from any Redis server can replicate to any number of replicas. A replica may be a master to another replica. This allows Redis to implement a single-rooted replication tree. Redis replicas can be configured to accept writes, permitting intentional and unintentional inconsistency between instances. The publish–subscribe feature is fully implemented, so a client of a replica may subscribe to a channel and receive a full feed of messages published to the master, anywhere up the replication tree. Replication is useful for read (but not write) scalability or data redundancy.[61]
Performance
When the durability of data is not needed, the in-memory nature of Redis allows it to perform well compared to database systems that write every change to disk before considering a transaction committed.[7] Redis operates as a single process and is single-threaded or double-threaded when it rewrites the AOF (append-only file).[62] Thus, a single Redis instance cannot use parallel execution of tasks such as stored procedures.
Clustering
Redis introduced clustering in April 2015 with the release of version 3.0.[63] The cluster specification implements a subset of Redis commands: all single-key commands are available, multi-key operations (commands related to unions and intersections) are restricted to keys belonging to the same node, and commands related to database selection operations are unavailable.[64] A Redis cluster can scale up to 1,000 nodes, achieve "acceptable" write safety and to continue operations when some nodes fail.[65][66]
Use cases
Due to the nature of the database design, typical use cases are session caching, full page cache, message queue applications, leaderboards and counting among others.[67] The publish–subscribe messaging paradigm allows real-time communication between servers.
