Azure Service Bus

Overview

We design Service Bus queues and topics for work that must not be lost: orders, integration messages, and commands between applications. Sessions, duplicate detection, and dead-letter queues are turned on where the message pattern needs them, and left off where they would only add cost.

We set shared access or, preferably, managed identity for each publisher and consumer, plus alerts when the dead-letter count rises. Message contracts are written down so a new consumer does not guess the body.

What we deliver

• Queues or topics with lock duration, sessions, and dead-lettering
• Duplicate detection or partitioning where the message pattern needs it
• Managed identity access for each publisher and consumer
• Message contract and an alert on dead-letter growth

Business benefits

• A downstream outage queues work instead of failing the caller
• Poison messages land in the dead-letter queue where they can be inspected
• Each application has its own identity, not a shared connection string in config