Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes
I would like to use the redis pub/sub mechanism to create a messaging system within our architecture. However, it seems that the pub/sub is possible only when there are multiple clients connected to a single host or in a master slave replication setup.
However, our servers are spread across the globe and we have 7 major sites where we have a redis host on each site acting as a master. Is there a way we can establish a pub/sub mechanism between the masters? We do not want to make any of the 7 master servers a slave so that is outside the question. We do not want to introduce delays etc. Also we want every site to be able to publish and other sites to subscribe to them. Essentially have 7 different channels and each site subscribing to 6 channels and publishing to 1 (its main channel).
Is this sort of a design architecture possible with redis?
Hi,
I would like to use the redis pub/sub mechanism to create a messaging system within our architecture. However, it seems that the pub/sub is possible only when there are multiple clients connected to a single host or in a master slave replication setup.
However, our servers are spread across the globe and we have 7 major sites where we have a redis host on each site acting as a master. Is there a way we can establish a pub/sub mechanism between the masters? We do not want to make any of the 7 master servers a slave so that is outside the question. We do not want to introduce delays etc. Also we want every site to be able to publish and other sites to subscribe to them. Essentially have 7 different channels and each site subscribing to 6 channels and publishing to 1 (its main channel).
Is this sort of a design architecture possible with redis?
Thanks, Purnashree