Summary

  • 3 minutes

In this module, you created a Service Bus namespace, a queue, a topic, and a subscription to the topic in your Azure subscription. Then, you sent and received messages through the queue and the topic by using C# code.

Service Bus queues and topics are excellent tools you can use to increase the resilience of communications within a distributed application. By acting as temporary storage locations, Service Bus queues and topics remove the requirement for direct communication between components, and they smoothly handle peaks in demand. Consider using Service Bus queues and topics when you have a component that can communicate with another component in a loosely coupled configuration.

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources that you leave running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Check your knowledge

1.

Which of the following queues should you use if you need FIFO message order and support for transactions?

2.

Suppose you're sending a message with Azure Service Bus and you want multiple components to receive it. Which Azure Service Bus feature should you use?

3.

True or false: You can add a message that's 20 MB in size to an Azure Service Bus queue.