Difference between revisions of "Redis Storage Driver Design (Zaqar)"
Prashanthr (talk | contribs) (Creating the page) |
Prashanthr (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | + | === Objective === | |
| + | |||
| + | Redis is an in memory key-value datastore which can organize data as strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs. Being In-memory makes it in ideal candidate for high load, low latency messages. | ||
| + | |||
| + | The main use cases of the driver are listed below: | ||
| + | |||
| + | 1. High-throughput (2K+ messages/sec per queue) | ||
| + | 2. Lots of small messages (<= 1K) | ||
| + | 3. Messages are short-lived (minutes, not hours) | ||
| + | 4. High durability is optional (2 copies, RAM only) | ||
| + | 5. HA is still very important | ||
| + | |||
| + | === Components of the basic driver === | ||
| + | |||
| + | |||
| + | === Current Status === | ||
| + | |||
| + | |||
| + | === Blueprints === | ||
| + | |||
| + | |||
| + | === Submitted Patches === | ||
Revision as of 04:27, 9 August 2014
Contents
Objective
Redis is an in memory key-value datastore which can organize data as strings, hashes, lists, sets, sorted sets, bitmaps and hyperloglogs. Being In-memory makes it in ideal candidate for high load, low latency messages.
The main use cases of the driver are listed below:
1. High-throughput (2K+ messages/sec per queue) 2. Lots of small messages (<= 1K) 3. Messages are short-lived (minutes, not hours) 4. High durability is optional (2 copies, RAM only) 5. HA is still very important
