A Ruby client library for Redis.
A Ruby client that tries to match Redis' API one-to-one, while still providing an idiomatic interface. It features thread-safety, client-side sharding, pipelining, and an obsession for performance.
Upgrading from 2.x to 3.0
Please refer to the CHANGELOG for a summary of the most important changes, as well as a full list of changes.
As of version 2.0 this client only targets Redis version 2.0 and higher. You can use an older version of this client if you need to interface with a Redis instance older than 2.0, but this is no longer supported.
You can connect to Redis by instantiating the
require "redis" redis = Redis.new
This assumes Redis was started with a default configuration, and is
localhost, port 6379. If you need to connect to a remote
server or a different port, try:
redis = Redis.new(:host => "10.0.1.1", :port => 6380, :db => 15)
You can also specify connection options as an URL:
redis = Redis.new(:url => "redis://:email@example.com:6380/15")
By default, the client will try to read the
REDIS_URL environment variable
and use that as URL to connect to. The above statement is therefore equivalent
to setting this environment variable and calling
Redis.new without arguments.
To connect to Redis listening on a Unix socket, try:
redis = Redis.new(:path => "/tmp/redis.sock")
To connect to a password protected Redis instance, use:
redis = Redis.new(:password => "mysecret")
The Redis class exports methods that are named identical to the commands
they execute. The arguments these methods accept are often identical to
the arguments specified on the Redis website. For
GET commands can be called like this:
redis.set("mykey", "hello world") # => "OK" redis.get("mykey") # => "hello world"
All commands, their arguments and return values are documented, and available on rdoc.info.
Redis only stores strings as values. If you want to store an object, you can use a serialization mechanism such as JSON:
require "json" redis.set "foo", [1, 2, 3].to_json # => OK JSON.parse(redis.get("foo")) # => [1, 2, 3]
When multiple commands are executed sequentially, but are not dependent, the calls can be pipelined. This means that the client doesn't wait for reply of the first command before sending the next command. The advantage is that multiple commands are sent at once, resulting in faster overall execution.
The client can be instructed to pipeline commands by using the
#pipelined method. After the block is executed, the client sends all
commands to Redis and gathers their replies. These replies are returned
redis.pipelined do redis.set "foo", "bar" redis.incr "baz" end # => ["OK", 1]
Executing commands atomically
You can use
MULTI/EXEC to run a number of commands in an atomic
fashion. This is similar to executing a pipeline, but the commands are
preceded by a call to
MULTI, and followed by a call to
the regular pipeline, the replies to the commands are returned by the
redis.multi do redis.set "foo", "bar" redis.incr "baz" end # => ["OK", 1]
Replies to commands in a pipeline can be accessed via the futures they
emit (since redis-rb 3.0). All calls inside a pipeline block return a
Future object, which responds to the
#value method. When the
pipeline has succesfully executed, all futures are assigned their
respective replies and can be used.
redis.pipelined do @set = redis.set "foo", "bar" @incr = redis.incr "baz" end @set.value # => "OK" @incr.value # => 1
inherit_socket: true: disable safety check that prevents a forked child from sharing a socket with its parent; this is potentially useful in order to mitigate connection churn when:
- many short-lived forked children of one process need to talk to redis, AND
- your own code prevents the parent process from using the redis connection while a child is alive
Improper use of
inherit_socketwill result in corrupted and/or incorrect responses.
By default, redis-rb uses Ruby's socket library to talk with Redis. To use an alternative connection driver it should be specified as option when instantiating the client object. These instructions are only valid for redis-rb 3.0. For instructions on how to use alternate drivers from redis-rb 2.2, please refer to an older README.
The hiredis driver uses the connection facility of hiredis-rb. In turn, hiredis-rb is a binding to the official hiredis client library. It optimizes for speed, at the cost of portability. Because it is a C extension, JRuby is not supported (by default).
It is best to use hiredis when you have large replies (for example:
ZRANGE, etc.) and/or use big pipelines.
In your Gemfile, include hiredis:
gem "redis", "~> 3.0.1" gem "hiredis", "~> 0.4.5"
When instantiating the client object, specify hiredis:
redis = Redis.new(:driver => :hiredis)
The synchrony driver adds support for em-synchrony. This makes redis-rb work with EventMachine's asynchronous I/O, while not changing the exposed API. The hiredis gem needs to be available as well, because the synchrony driver uses hiredis for parsing the Redis protocol.
In your Gemfile, include em-synchrony and hiredis:
gem "redis", "~> 3.0.1" gem "hiredis", "~> 0.4.5" gem "em-synchrony"
When instantiating the client object, specify synchrony:
redis = Redis.new(:driver => :synchrony)
This library is tested using Travis, where it is tested against the following interpreters and drivers:
- MRI 1.8.7 (drivers: ruby, hiredis)
- MRI 1.9.2 (drivers: ruby, hiredis, synchrony)
- MRI 1.9.3 (drivers: ruby, hiredis, synchrony)
- MRI 2.0.0 (drivers: ruby, hiredis, synchrony)
- JRuby 1.7 (1.8 mode) (drivers: ruby)
- JRuby 1.7 (1.9 mode) (drivers: ruby)
(ordered chronologically with more than 5 commits, see
git shortlog -sn for
- Ezra Zygmuntowicz
- Taylor Weibley
- Matthew Clark
- Brian McKinney
- Luca Guidi
- Salvatore Sanfillipo
- Chris Wanstrath
- Damian Janowski
- Michel Martens
- Nick Quaranto
- Pieter Noordhuis
- Ilya Grigorik
Fork the project and send pull
requests. You can also ask for help at
#redis-rb on Freenode.