Partitioned queues/topics
Without partitions, a queue or topic is handled by a single message broker and stored in a single messaging store, which can constrain performance. Using partitions, a queue or topic can be spread across multiple brokers and stores, thereby providing a higher throughput rate than a single message broker and store. These partitions contain all the features of a no partitioned queue or topic, such as transactions and sessions.
When messages arrive at the queue or topic, they are distributed in a round-robin fashion to all the fragments of a partitioned queue or topic if no partition key has been defined.
To control which fragment receives what message, the properties SessionId, PartitionKey, and MessageId may be used as partition ...
Get Robust Cloud Integration with Azure now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
