Just like ActiveMQ, Redis Pub/Sub publishers and subscribers are independent of each other. So, when the first of them sends a message, it doesn't know what receivers are connected to that channel. This is also true for the receivers that subscribe to channels, without knowledge of other publishers.
One of the main advantages of this technology is the opportunity to use clients written in different languages. You can read the full list
. It includes such popular solutions, as Ruby, Python, PHP, Objective-C, Node.js, Java, Clojure, C++, C#, etc.
Using Redis' Pub/Sub within your infrastructure, you will enjoy quick messaging and communication between processes. The broker's simplicity
make it popular for a wide range of use cases. Taking into account the famous database and the cache feature, Redis can become a handy technology for your future project.
Here we end our journey through the self deploy
messaging systems. Let me know if you like such reviews and your opinions about all of these technologies. Do you want to get more information about cloud message brokers
(AWS SQS, SNS, Amazon Kinesis, GCP Pub/Sub, Microsoft Azure, etc.)? Subscribe to FreshCode blog to learn more about software development
Don't miss the previous part of this article: Apache Kafka vs Rabbit MQ