So, an event bus fullfills a very similar purpose like an event queue, but it does not necessarily provide any FIFO guarantees. Although Publish/Subscribe is based on earlier design patterns like message queuing and event brokers, it is more flexible and scalable. Subscribers subscribe to the certain type of event at that that bus, and publishers raise the events there. Pub/Sub (or Publish/Subscribe) is an architectural design pattern used in distributed systems for asynchronous communication between different components or services. Queue will save the message and wait until someone requests the message. Pub/Sub will drop the message if there is no one subscribing to the channel at the time. This blog post is the second part of the summary of our analysis and our choice. Then, we set the consumers’ groupIds with the same. We recently started on a new project where we narrowed down our choices to these two products. Starting with Queues, suppose we have multiple consumers, but we only want each message to be processed once. Queue only gives a message to the one who requests the message first. RabbitMQ and Google Pub/Sub are both powerful and reliable message queue implementations, and if you need to pick one of them for your Google Cloud Platform (GCP) project, the choice may not be simple. The event bus has a life time as long as your application or system runs. Pub/Sub will broadcast a message to everyone subscribing to the channel. However, when you have a system where you have certain event publishers for a certain type of event, and you may also have subscribers for this type of event, and the life times of publishers and subscribers is completely independent from each other, you need a middle-man component to manage this. There are lots of simple scenarios where this is sufficient. Google Cloud Pub/Sub is a scalable, durable event ingestion and message delivery system that allows you to create an infrastructure whose responsibility is.

This means the life time of the event publishers is as least as long or longer than any of its subscribers. For the 'publisher/subscriber' pattern, subscriber components have to subscribe (or unsubscribe) to an event publisher.

Pub sub message queue