Azure Event Grid
Event Grid is a highly scalable, serverless mediator that you can use to connect different applications through events. To subscriber destinations like applications, Azure services, or any other endpoint to which Event Grid has network access, events are provided by Event Grid. Other applications, SaaS services, and Azure services may be the origin of those occurrences.
Key Words
- Events – What happened?
- Event sources – Where the event took place.
- Topics – The endpoint where publishers send events.
- Event subscriptions – It refers to the destination or pre-existing system used to direct events to one or more event handlers. Handlers can use subscriptions to selectively receive only relevant events.
- Event handlers – The app or service reacting to the event.
Event Sources
- User’s own service or solution: Event Grid allows you to publish your own events, and your customers can subscribe to them. There are two options available: Custom Topics or Domains, depending on your needs. Use Custom Topics if you want to control the event handling process, and use Domains if you want to deliver events to multiple teams.
- Saas provider or platform: A company that provides software as a service can send their events to Event Grid using a feature called Partner Events. You can then subscribe to those events and automate tasks. Currently, events from partners like Auth0 and Microsoft Graph API are available.
- An Azure Service: Some of the Azure services that can send events to Event Grid are:
- Azure Blob Storage
- Azure Event Hubs
- Azure IoT Hub
- Azure Service Bus
- Azure subscriptions
Event Handlers
These Azure services can currently handle events from Event Grid:
- Webhooks
- Azure functions
- Event Hubs
- Service Bus queues and topics
- Relay hybrid connections
- Storage queues
How To Set Up Azure Event Grid?
Event Grid is like a notification service that lets different computer programs (like apps or services) talk to each other and send messages when something happens. It can be used when you want to automatically trigger a reaction in one program based on something happening in another program.