diff options
| author | antirez <antirez@gmail.com> | 2015-04-29 10:34:08 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2015-04-29 10:34:08 +0200 |
| commit | 7af420e78dea827fdc37d51da47b2b3b7e4bc63e (patch) | |
| tree | 35f7b32572d6b2e7e43ad08e6788ff37a47bb806 | |
| parent | 9e7f39d29dbd382212478f1c425ca4dcba89228b (diff) | |
| parent | fe0d71d52f53ec8675e8bbcfe4efc4e6f45771c0 (diff) | |
| download | redis-7af420e78dea827fdc37d51da47b2b3b7e4bc63e.tar.gz | |
Merge branch 'unstable' of github.com:/antirez/redis into unstable
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -3,15 +3,15 @@ This README is just a fast *quick start* document. You can find more detailed do What is Redis? -------------- -Redis is often referred as a *data structures* server. What this means is that Redis provides access to mutable data structures via a set of commands, which are send using a *server-client* model with TCP sockets and a simple protocol. So different processes can query and modify the same data structures in a shared way. +Redis is often referred as a *data structures* server. What this means is that Redis provides access to mutable data structures via a set of commands, which are sent using a *server-client* model with TCP sockets and a simple protocol. So different processes can query and modify the same data structures in a shared way. Data structures implemented into Redis have a few special properties: * Redis cares to store them on disk, even if they are always served and modified into the server memory. This means that Redis is fast, but that is also non-volatile. * Implementation of data structures stress on memory efficiency, so data structures inside Redis will likely use less memory compared to the same data structure modeled using an high level programming language. -* Redis offers a number of features that are natural to find into a database, like replication, tunable levels of durability, cluster, high availability. +* Redis offers a number of features that are natural to find in a database, like replication, tunable levels of durability, cluster, high availability. -Another good example is to think at Redis as a more complex version of memcached, where the opeations are not just SETs and GETs, but operations to work with complex data types like Lists, Sets, ordered data structures, and so forth. +Another good example is to think of Redis as a more complex version of memcached, where the operations are not just SETs and GETs, but operations to work with complex data types like Lists, Sets, ordered data structures, and so forth. If you want to know more, this is a list of selected starting points: |