Service Bus

In the Ultra Transcenders books

AZ-305AZ-104

Each book explains Service Bus in context, with comparison tables and the common traps.

Terms in this definition

• Enterprise

  Any group of organisations with shared goals. Examples range from an entire company or one of its divisions to a government department, or several organisations working as partners or along a supply chain.

Related terms

• AMQP

  Short for Advanced Message Queuing Protocol; Service Bus and Event Hubs accept it as well as HTTPS.

• Auto-delete on idle

  Once a Service Bus queue, topic or subscription has gone unused for a chosen period (five minutes at the very least), this setting removes it automatically.

• Azure Service Bus Data Owner

  Grants complete control over Service Bus data operations, meaning it can send and receive messages as well as manage entities and filters. If an app needs only one direction, Data Sender or Data Receiver keep permissions tighter.

• Dapr components

  Connect Dapr APIs in Azure Container Apps to the services behind them, such as a state store on Cosmos DB or pub/sub on Service Bus. They are defined at environment level, and each one's scopes list names the Dapr app IDs allowed to load it.

• Dead-letter queue

  Each Service Bus queue and subscription automatically has this secondary queue, where messages end up when they can't be delivered or processed. You never create it yourself, message TTL has no effect there, and nothing in it is removed unless you remove it.

• Duplicate detection

  A Service Bus option that drops any incoming message whose MessageId, set by the sending application, matches one already received during a chosen time window.

• FIFO

  First in, first out: messages are processed in strict order. Service Bus achieves this with message sessions, which Storage queues can't offer.

• JMS

  An API for messaging in Java. Service Bus Premium supports version 2.0, whereas Standard offers only part of JMS 1.1.