For most messaging scenarios, Azure Event Grid should be the first choice. It has the capability to push messages simultaneously to several targets such as Azure Service Bus, Azure Logic Apps, custom webhooks, and much more.
Event Grid is a service for managing routing of all events from any source to any destination.
Instead of the polling model used by a service bus, with Event Grid, event publishers are decoupled from event subscribers using a pub/sub model and simple HTTP-based event delivery, allowing you to build scalable serverless applications, microservices, and distributed systems.
Many message destinations are available for Event Grid, including but not limited to: Service Bus, Azure Functions, Logic Apps, webhooks, and many more.
To easily consume Azure Event Grid functionality, connect to the NuGet feed in the Artifacts section of Azure DevOps and download the shared client library “Shared.Messaging.EventGridConsumer”.
If the application need is for a true publish/subscribe model for messaging, then Azure Service Bus should be used.
Azure Service Bus is a fully managed enterprise integration message broker. Service Bus can decouple applications and services. Service Bus offers a reliable and secure platform for asynchronous transfer of data and state.
To easily consume Azure Service Bus functionality, connect to the NuGet feed in the Artifacts section of Azure DevOps and download the shared client library “Shared.Messaging.ServiceBusConsumer”.
If the application needs a simple queue, then Azure Storage Queues should be used.
To easily consume Azure Storage Queues functionality, connect to the NuGet feed in the Artifacts section of Azure DevOps and download the shared client library “Shared.Messaging.StorageQueueConsumer”.
PREVIOUS: File Storage
Solution Architecture Guidance
NEXT: Batch Jobs and Scheduled Processing