Difference between revisions of "Redis Storage Driver Design (Zaqar)"
Prashanthr (talk | contribs) (→Blueprints) |
Prashanthr (talk | contribs) (→Current Status) |
||
| Line 21: | Line 21: | ||
=== Current Status === | === Current Status === | ||
| + | The basic driver is a "Work in Progress" and is expected to be a part of the code base by Juno-3 deadline (Sept 4th 2014). The clustering and persistence extension is expected to be developed before the end of Kilo. | ||
=== Blueprints === | === Blueprints === | ||
Revision as of 04:37, 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
Components of the basic driver
Current Status
The basic driver is a "Work in Progress" and is expected to be a part of the code base by Juno-3 deadline (Sept 4th 2014). The clustering and persistence extension is expected to be developed before the end of Kilo.
Blueprints
| Blueprint URL | Functionality |
|---|---|
| [1] | Redis as an alternative driver for MongoDB |
| [2] | Redis Storage Driver for Marconi |
Submitted Patches
| Patch URL | Implemented Feature |
|---|---|
| [3] | Messages and Queue Controllers |
| [4] | Claims Controller |
| [5] | Pools and Catalog Controllers |
