Difference between revisions of "Redis Storage Driver Design (Zaqar)"
Prashanthr (talk | contribs) |
Prashanthr (talk | contribs) |
||
| Line 5: | Line 5: | ||
The main use cases of the driver are listed below: | The main use cases of the driver are listed below: | ||
| − | 1. High-throughput (2K+ messages/sec per queue) | + | 1. High-throughput (2K+ messages/sec per queue)<br /> |
| − | 2. Lots of small messages (<= 1K) | + | |
| − | 3. Messages are short-lived (minutes, not hours) | + | 2. Lots of small messages (<= 1K)<br /> |
| − | 4. High durability is optional (2 copies, RAM only) | + | |
| − | 5. HA is still very important | + | 3. Messages are short-lived (minutes, not hours)<br /> |
| + | |||
| + | 4. High durability is optional (2 copies, RAM only)<br /> | ||
| + | |||
| + | 5. HA is still very important<br /> | ||
| + | |||
=== Components of the basic driver === | === Components of the basic driver === | ||
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
