Redis is an open-source, networked, in-memory, key-value data store with optional durability. It is written in ANSI C. The development of Redis has been sponsored by Pivotal Software since May 2013; before that, it was sponsored by VMware. According to the monthly ranking by, Redis is the most popular key-value store. The name Redis means REmote DIctionary Server.


Supported languages

Many languages have Redis bindings, including: ActionScript, C, C++, C#, Clojure, Common Lisp, Dart, Erlang, Go, Haskell, Haxe, Io, Java, JavaScript (Node.js), Lua, Objective-C, Perl, PHP, Pure Data, Python, R, Ruby, Scala, Smalltalk and Tcl.


Data models

In its outer layer, the Redis data model is a dictionary, which maps keys to values. One of the main differences between Redis and other structured storage systems is that Redis supports not only strings, but also abstract data types:

  • Lists of strings
  • Sets of strings (collections of non-repeating unsorted elements)
  • Sorted sets of strings (collections of non-repeating elements ordered by a floating-point number called score)
  • Hashes where keys and values are strings

The type of a value determines what operations (called commands) are available for the value itself. Redis supports high-level, atomic, server-side operations like intersection, union, and difference between sets and sorting of lists, sets and sorted sets.



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 in which some of the dataset is stored on disk, but this feature is deprecated. Persistence is now reached in two different ways: one is called snapshotting, and is a semi-persistent durability mode where the dataset is asynchronously transferred from memory to disk from time to time, written in RDB dump format. Since version 1.1 the safer alternative is AOF, an append-only file (a journal) that is written as operations modifying the dataset in memory are processed. Redis is able to rewrite the append-only file in the background in order to avoid an indefinite growth of the journal.

By default, Redis syncs data to the disk 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.



Redis supports master-slave replication. Data from any Redis server can replicate to any number of slaves. A slave may be a master to another slave. This allows Redis to implement a single-rooted replication tree. Redis slaves are writable, permitting intentional and unintentional inconsistency between instances. The Publish/Subscribe feature is fully implemented, so a client of a slave 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.



When the durability of data is not needed, the in-memory nature of Redis allows it to perform extremely well compared to database systems that write every change to disk before considering a transaction committed. There is no notable speed difference between write and read operations. Redis operates as a single process and single-threaded. Therefore a single Redis instance cannot utilize parallel execution of tasks e.g. stored procedures (Lua scripts).



The Redis project has a cluster specification, but the cluster feature is currently in Beta stage. According to a news post by Redis creator Sanfilippo, the first production version of Redis cluster (planned for beta release at end of 2013), will support automatic partitioning of the key space and hot resharding, but will support only single key operations. In future Redis Cluster is planned to support up to 1000 nodes, fault tolerance with heartbeat and failure detection, incremental versioning (“epochs”) to prevent conflicts, slave election and promotion to master, and publish/subscribe between all cluster nodes. 


Cloud deployment

Redis is commonly deployed on IaaS or PaaS platforms like Amazon Web Services, Rackspace, ObjectRocket or Heroku.

  • On IaaS platforms, it is possible to deploy Redis by uploading a virtual machine image, with Redis installed, to a cloud machine instance. Alternatively, it is possible to install Redis on an already-running machine instance.
  • On Amazon EC2, Redis can be installed on a running machine instance using the script
  • On Windows Azure, Redis can be installed on a Centos Linux VM by following these instructions.
  • On Joyent, Redis can be installed using these instructions.

On both IaaS and PaaS platforms, there are commercial database as a service providers which allow applications to use Redis as a managed service, without manually launching a virtual machine instance for the database. These services handle installation, configuration and maintenance of Redis on behalf of the application owner. Following are notable examples of commercial Redis database as a service providers.

Like what you see? Contact us for a quote.

Get a quote in 10 minutes for any app or web project.