A very detailed article about creating a message queue (nb: not Pub/Sub) using Redis:
One particular combination has recently allowed us to implement a
moderately (read: good enough) reliable message delivery mechanism
for multiple consumers consuming messages at their own pace.
Redis allowed for all of the implementation characteristics we were looking for, namely:
- Concurrency: Because all operations in Redis are atomic, supporting concurrency without too much of a hassle is straightforward.
- Persistence: Configured properly, we can ensure persistence of our queues to disk using one of the supported Redis persistence strategies.
- Lightweight: Using Redis from any language/platform is extremely simple and provisioning it / maintaining it on a production server is dead easy.
I’m always saying to use the right tool for the job, but maintaining the simplicity of a system architecture is an art too.
Original title and link: Reliable Delivery Message Queues With Redis ( ©myNoSQL)