We use 0MQ and Redis together at work. We have an incremental flow of updates that we distribute internally over 0MQ pubsub, and have one listener process that updates the full state in Redis from each update message. That way, we have both (a) a way to easily get the latest state (and fast), and (b) an easy way to listen for updates to the state. It works beautifully, even with a high rate of updates.
back
1 comments
Forgive my ignorance, but why 0MQ pubsub and not redis pubsub?
0MQ pubsub can be trivially distributed, whereas redis is currently limited to master-slave replication (as opposed to master-master).