Example 1 – Working with priority queues in Azure Service Bus

When you use Service Bus queues for an enterprise application, communication messages are picked up based the FIFO pattern. This means if a queue's length is 100, then a high-priority message will only be delivered after the subscribing application reads and commits all of the previous 100 messages.

To deal with this scenario, one option is to create separate queues for high-priority and low-priority messages, and the client application will be in control of setting up a queue endpoint when publishing a message to Service Bus queues:

The code for routing the message to separate ...

Get Serverless Integration Design Patterns 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.