Azure Event Hubs provides big data applications the capability to process large volume of data. It can also scale out during exceptionally high-demand periods as and when required. Azure Event Hubs decouples the sending and receiving messages to manage the data processing. This helps eliminate the risk of overwhelming consumer application and data loss because of any unplanned interruptions.

In this module, you've seen how to deploy Azure Event Hubs as part of an event processing solution.

You learned how to:

  • Use the Azure CLI commands to create an Event Hubs namespace and an event hub in that namespace.
  • Configure sender and receiver applications to send and receive messages through the event hub.
  • Use the Azure portal to view your event hub status and performance.

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 left 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


Applications that publish messages to Azure Event Hub very frequently will get the best performance using Advanced Message Queuing Protocol (AMQP) because it establishes a persistent socket.


By default, how many partitions will a new Event Hub have?


What is the maximum size for a single publication (individual or batch) that is allowed by Azure Event Hub?