Contents
What is difference between pub/sub and message queue?
In a message-queue model, the publisher pushes messages to a queue where each subscriber can listen to a particular queue. In the event-stream model using Pub/Sub, the publisher pushes messages to a topic that multiple subscribers can listen to.
How many SQS queues can I have?
There is no limit for the number of queues and for the number of messages in a queue. There is no limit to the number of queues you can create: Q: How many message queues can I create? You can create any number of message queues.
How are topics and subscriptions different from queues?
Topics and subscriptions. In contrast to queues, in which each message is processed by a single consumer, topics and subscriptions provide a one-to-many form of communication, in a publish/subscribe pattern. Useful for scaling to large numbers of recipients, each published message is made available to each subscription registered with the topic.
How are messages delivered to consumers in queues?
Irrespective of the consumer status (Live, slow and offline), there is no message loss to any of the consumers. Messages will be delivered to each consumer as and when they are ready to consume. As long as the queue quota is not reached, messages keep accumulating on the endpoint until they are consumed or expire.
How is service bus different from virtual subscription queue?
While Service Bus subscriptions see all messages sent to the topic, you can only copy a subset of those messages to the virtual subscription queue. This filtering is accomplished using subscription filters. Such modifications are called filter actions.
Are there durable topic subscriptions in JMS queues?
Since JMS durable subscribers do offer queue like message reliability to topic subscribers, using that would be another option. If the consumer is interested in only a single topic (e.g S2 and S4 in the example above), they can create a durable subscriptions to topics. This is offered in Solace as well with durable topic endpoint (DTE).