Watch a comparison of Azure Service Bus vs. Event Grid, Event Hub, and Storage Queue.
- [Narrator] Now those of you familiar with Azure, must be thinking, why do we need yet another messaging service, don't we already have enough? Well, Azure, at a high level, you could say contains the following messaging services ... Event Grid, Event Hubs, Storage Queues and Service Bus. All of these, provide unique architectural advantages and are uniquely suited to certain purposes. Let's find out which is suited for which purpose.
Event Grid. The focus of this course. Well that's great for reactive programming. You have the ability to distribute events but an event is considered as a discrete object. Yeah, you can send arrays of events but still, it's an event or a few events and applications can react to changes. Event Hub, on the other hand, is about a big data pipeline, think IoT. Millions of devices streaming a lot of information.
So it's more about event streaming and you don't want to miss that information. The events come in series, and it's all about telemetry and distributed data streaming. That's the right applications for it. Service Bus on the other hand, well that is more for high-value enterprise messaging. Say an invoice card approved and therefore a payment must be processed, so the message, that invoice approved message could be sent over. Remember the word message.
So it's sending messages, not events. So things like order processing, financial transactions, think more business. That is what Service Bus is good for.
- What is Azure Event Grid?
- Security and authentication
- Delivery and retry
- Using Event Grid with Azure Blog Storage