112 lines
14 KiB
HTML
112 lines
14 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
|
<html>
|
|
<head>
|
|
<link type="text/css" rel="stylesheet" href="style.css" />
|
|
</head>
|
|
<body>
|
|
<div id="page">
|
|
|
|
<div id='header'>
|
|
<a href="index.html">
|
|
<img style="border:none" alt="Redis Documentation" src="redis.png">
|
|
</a>
|
|
</div>
|
|
|
|
<div id="pagecontent">
|
|
<div class="index">
|
|
<!-- This is a (PRE) block. Make sure it's left aligned or your toc title will be off. -->
|
|
<b>README: Contents</b><br> <a href="#Introduction">Introduction</a><br> <a href="#Beyond key-value databases">Beyond key-value databases</a><br> <a href="#What are the differences between Redis and Memcached?">What are the differences between Redis and Memcached?</a><br> <a href="#What are the differences between Redis and Tokyo Cabinet / Tyrant?">What are the differences between Redis and Tokyo Cabinet / Tyrant?</a><br> <a href="#Does Redis support locking?">Does Redis support locking?</a><br> <a href="#Multiple databases support">Multiple databases support</a><br> <a href="#Redis Data Types">Redis Data Types</a><br> <a href="#Implementation Details">Implementation Details</a><br> <a href="#Redis Tutorial">Redis Tutorial</a><br> <a href="#License">License</a><br> <a href="#Credits">Credits</a>
|
|
</div>
|
|
|
|
<h1 class="wikiname">README</h1>
|
|
|
|
<div class="summary">
|
|
|
|
</div>
|
|
|
|
<div class="narrow">
|
|
<h1><a name="Introduction">Introduction</a></h1>Redis is a database. To be more specific redis is a very simple database
|
|
implementing a dictionary where keys are associated with values. For example
|
|
I can set the key "surname_1992" to the string "Smith".<br/><br/>Redis takes the whole dataset in memory, but the dataset is persistent
|
|
since from time to time Redis writes a dump of the dataset on disk asynchronously. The dump is loaded every time the server is restarted. This means that if a system crash occurs the last few queries can get lost (that is acceptable in many applications). Redis supports master-slave replication from the early days in order to improve performances and reliability.<h1><a name="Beyond key-value databases">Beyond key-value databases</a></h1>In most key-value databases keys and values are simple strings. In Redis keys are just strings too, but the associated values can be Strings, Lists and Sets, and there are commands to perform complex atomic operations against this data types, so you can think at Redis as a data structures server.<br/><br/>For example you can append elements to a list stored at the key "mylist" using the LPUSH or RPUSH operation in O(1). Later you'll be able to get a range of elements with LRANGE or trim the list with LTRIM. Sets are very flexible too, it is possible to add and remove elements from Sets (unsorted collections of strings), and then ask for server-side intersection, union, difference of Sets.<br/><br/>All this features, the support for sorting Lists and Sets, allow to use Redis as the sole DB for your scalable application without the need of any relational database. <a href="TwitterAlikeExample.html">We wrote a simple Twitter clone in PHP + Redis</a> to show a real world example, the link points to an article explaining the design and internals in very simple words.<h1><a name="What are the differences between Redis and Memcached?">What are the differences between Redis and Memcached?</a></h1>In the following ways:<br/><br/><ul><li> Memcached is not persistent, it just holds everything in memory without saving since its main goal is to be used as a cache. Redis instead can be used as the main DB for the application. We <a href="TwitterAlikeExample.html">wrote a simple Twitter clone</a> using only Redis as database.</li></ul>
|
|
<ul><li> Like memcached Redis uses a key-value model, but while keys can just be strings, values in Redis can be lists and sets, and complex operations like intersections, set/get n-th element of lists, pop/push of elements, can be performed against sets and lists. It is possible to use lists as message queues.</li></ul>
|
|
<h1><a name="What are the differences between Redis and Tokyo Cabinet / Tyrant?">What are the differences between Redis and Tokyo Cabinet / Tyrant?</a></h1>Redis and Tokyo Cabinet can be used for the same applications, but actually they are <b>very</b> different beasts:<br/><br/><ul><li> Tokyo Cabinet writes synchronously on disk, Redis takes the whole dataset on memory and writes on disk asynchronously. Tokyo Cabinet is safer, Redis faster (but note that Redis supports master-slave replication that is trivial to setup, so you are safe anyway if you want a setup where data can't be lost even after a disaster).</li></ul>
|
|
<ul><li> Redis supports higher level operations and data structures. While Tokyo Cabinet supports a kind of database that is able to organize data into rows with named fields (in a way very similar to Berkeley DB) can't do things like server side List and Set operations Redis is able to do: pushing or popping from Lists in an atomic way, in O(1) time complexity, server side Set intersections, <a href="SORT.html">SortCommand</a> ing of schema free data in complex ways (Btw TC supports sorting in the table-based database format).</li></ul>
|
|
<ul><li> Tokyo Cabinet does not implement a networking layer. You have to use a networking layer called Tokyo Tyrant that interfaces to Tokyo Cabinet so you can talk to Tokyo Cabinet in a client-server fashion. In Redis the networking support is built-in inside the server, and is basically the only interface between the external world and the dataset.</li></ul>
|
|
<ul><li> Redis is reported to be much faster, especially if you plan to access Tokyo Cabinet via Tokyo Tyrant. From the informal numbers I saw around on the net you can expect Redis to be 10 times faster than Tokyo Cabinet + Tyrant.</li></ul>
|
|
<ul><li> Redis is generally an higher level beast in the operations supported, and it is much simpler to get started. <a href="Check.html">the command reference CommandReference</a> to get a feeling. You can even start playing with Redis by telnet after reading the five minutes tutorial at the end of this README file. To implement new client libraries is trivial. <a href="Check.html">the protocol specification ProtocolSpecification</a> for more information.</li></ul><blockquote></blockquote><ul><li> Redis is not an on-disk DB engine like Tokyo: the latter can be used as a fast DB engine in your C project without the networking overhead just linking to the library. Still remember that in many scalable applications you need multiple servers talking with multiple clients, so the client-server model is almost always needed.</li></ul>
|
|
<h1><a name="Does Redis support locking?">Does Redis support locking?</a></h1>No, the idea is to provide atomic primitives in order to make the programmer
|
|
able to use redis with locking free algorithms. For example imagine you have
|
|
10 computers and 1 redis server. You want to count words in a very large text.
|
|
This large text is split among the 10 computers, every computer will process
|
|
its part and use Redis's INCR command to atomically increment a counter
|
|
for every occurrence of the word found.<br/><br/>INCR/DECR are not the only atomic primitives, there are others like PUSH/POP
|
|
on lists, POP RANDOM KEY operations, UPDATE and so on. For example you can
|
|
use Redis like a Tuple Space (<a href="http://en.wikipedia.org/wiki/Tuple_space" target="_blank">http://en.wikipedia.org/wiki/Tuple_space</a>) in
|
|
order to implement distributed algorithms.<br/><br/>(News: locking with key-granularity is now planned)<h1><a name="Multiple databases support">Multiple databases support</a></h1>Another synchronization primitive is the support for multiple DBs. By default DB 0 is selected for every new connection, but using the SELECT command it is possible to select a different database. The MOVE operation can move an item from one DB to another atomically. This can be used as a base for locking free algorithms together with the 'RANDOMKEY' or 'POPRANDOMKEY' commands.<h1><a name="Redis Data Types">Redis Data Types</a></h1>Redis supports the following three data types as values:<br/><br/><ul><li> Strings: just any sequence of bytes. Redis strings are binary safe so they can not just hold text, but images, compressed data and everything else.</li><li> Lists: lists of strings, with support for operations like append a new string on head, on tail, list length, obtain a range of elements, truncate the list to a given length, sort the list, and so on.</li><li> Sets: an unsorted set of strings. It is possible to add or delete elements from a set, to perform set intersection, union, subtraction, and so on.</li></ul>
|
|
Values can be Strings, Lists or Sets. Keys can be a subset of strings not containing newlines ("\n") and spaces (" ").<br/><br/>Note that sometimes strings may hold numeric vaules that must be parsed by
|
|
Redis. An example is the INCR command that atomically increments the number
|
|
stored at the specified key. In this case Redis is able to handle integers
|
|
that can be stored inside a 'long long' type, that is a 64-bit signed integer.<h2><a name="Implementation Details">Implementation Details</a></h2>Strings are implemented as dynamically allocated strings of characters.
|
|
Lists are implemented as doubly linked lists with cached length.
|
|
Sets are implemented using hash tables that use chaining to resolve collisions.<h1><a name="Redis Tutorial">Redis Tutorial</a></h1>(note, you can skip this section if you are only interested in "formal" doc.)<br/><br/>Later in this document you can find detailed information about Redis commands,
|
|
the protocol specification, and so on. This kind of documentation is useful
|
|
but... if you are new to Redis it is also BORING! The Redis protocol is designed
|
|
so that is both pretty efficient to be parsed by computers, but simple enough
|
|
to be used by humans just poking around with the 'telnet' command, so this
|
|
section will show to the reader how to play a bit with Redis to get an initial
|
|
feeling about it, and how it works.<br/><br/>To start just compile redis with 'make' and start it with './redis-server'.
|
|
The server will start and log stuff on the standard output, if you want
|
|
it to log more edit redis.conf, set the loglevel to debug, and restart it.<br/><br/>You can specify a configuration file as unique parameter:<br/><br/><blockquote>./redis-server /etc/redis.conf</blockquote>
|
|
This is NOT required. The server will start even without a configuration file
|
|
using a default built-in configuration.<br/><br/>Now let's try to set a key to a given value:<br/><br/><pre class="codeblock python" name="code">
|
|
$ telnet localhost 6379
|
|
Trying 127.0.0.1...
|
|
Connected to localhost.
|
|
Escape character is '^]'.
|
|
SET foo 3
|
|
bar
|
|
+OK
|
|
</pre>The first line we sent to the server is "set foo 3". This means "set the key
|
|
foo with the following three bytes I'll send you". The following line is
|
|
the "bar" string, that is, the three bytes. So the effect is to set the
|
|
key "foo" to the value "bar". Very simple!<br/><br/>(note that you can send commands in lowercase and it will work anyway,
|
|
commands are not case sensitive)<br/><br/>Note that after the first and the second line we sent to the server there
|
|
is a newline at the end. The server expects commands terminated by "\r\n"
|
|
and sequence of bytes terminated by "\r\n". This is a minimal overhead from
|
|
the point of view of both the server and client but allows us to play with
|
|
Redis with the telnet command easily.<br/><br/>The last line of the chat between server and client is "+OK". This means
|
|
our key was added without problems. Actually SET can never fail but
|
|
the "+OK" sent lets us know that the server received everything and
|
|
the command was actually executed.<br/><br/>Let's try to get the key content now:<br/><br/><pre class="codeblock python python" name="code">
|
|
GET foo
|
|
3
|
|
bar
|
|
</pre>Ok that's very similar to 'set', just the other way around. We sent "get foo",
|
|
the server replied with a first line that is just a number of bytes the value
|
|
stored at key contained, followed by the actual bytes. Again "\r\n" are appended
|
|
both to the bytes count and the actual data.<br/><br/>What about requesting a non existing key?<br/><br/><pre class="codeblock python python python" name="code">
|
|
GET blabla
|
|
nil
|
|
</pre>When the key does not exist instead of the length just the "nil" string is sent.
|
|
Another way to check if a given key exists or not is indeed the EXISTS command:<br/><br/><pre class="codeblock python python python python" name="code">
|
|
EXISTS nokey
|
|
0
|
|
EXISTS foo
|
|
1
|
|
</pre>As you can see the server replied '0' the first time since 'nokey' does not
|
|
exist, and '1' for 'foo', a key that actually exists.<br/><br/>Ok... now you know the basics, read the <a href="CommandReference.html">REDIS COMMAND REFERENCE</a> section to
|
|
learn all the commands supported by Redis and the <a href="ProtocolSpecification.html">PROTOCOL SPECIFICATION</a>
|
|
section for more details about the protocol used if you plan to implement one
|
|
for a language missing a decent client implementation.<h1><a name="License">License</a></h1>Redis is released under the BSD license. See the COPYING file for more information.<h1><a name="Credits">Credits</a></h1>Redis is written and maintained by Salvatore Sanfilippo, Aka 'antirez'.<br/><br/>Enjoy,
|
|
antirez
|
|
|
|
</div>
|
|
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|
|
|