Azure Service Bus

Overview

Official information

Namespaces

Namespaces are the scoping containers where our messaging components will live, like queues and topics.

Tiers

There are three tiers available that provide different functionality:

Basic for Queues and scheduled messages with a size of 256 KB
Standard will add tropics, transactions, de-duplication, sessions, and forwarding
Premium adds support for resource isolation, zone redundancy, availability zones, and increased message size to 1 MB

Compare the different tiers:

Feature	Basic	Standard	Premium
Queues	x	x	x
Scheduled messages	x	x	x
Topics		x	x
Transactions		x	x
De-duplication		x	x
Sessions		x	x
ForwardTo/SendVia		x	x
Message Size	256 KB	256 KB	1 MB
Resource isolation			x
Geo-Disaster Recovery			x
Availability Zones (AZ)			x
Partitioning	x	x

Feature

Queues support
Partitioning is only available in Basic or Standard tiers. It is not available for the Premium tier. Please see Partitioned queues and topics | Microsoft Docs for more information.

Protocol

Azure Service Bus supports either Advanced Message Queuing Protocol (AMQP) or Service Bus Messaging Protocol (SBMP) with the .NET client library for Service Bus. AMQP is the default protocol used by the .NET library. It is not recommended to override it, except for unsupported features which can be found at Azure Service Bus with .NET and AMQP 1.0 – Azure Service Bus | Microsoft Docs.

The Azure Service Bus cloud service uses the Advanced Message Queuing Protocol (AMQP) 1.0 as its primary communication. AMQP enables to build cross-platform, hybrid applications using a vendor-neutral and implementation-neutral, open standard protocol.

Integrations

Integrate with RabbitMQ

How to integrate RabbitMQ with Azure Service Bus – Azure Service Bus | Microsoft Docs