Appearance
Event Grid
Reliable event delivery at massive scale.
Use Event Grid to power your event-driven and serverless apps
Simplify your event-based apps with Event Grid, a single service for managing routing of all events from any source to any destination. Designed for high availability, consistent performance, and dynamic scale, Event Grid lets you focus on your app logic rather than infrastructure.
| Feature | Description |
|---|---|
| Simplify event delivery | Eliminate polling—and the associated cost and latency. 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. |
| Build reliable cloud applications | Gain massive scale, dynamically, while getting near-real-time notifications for changes you're interested in. Build better, more reliable applications through reactive programming, capitalizing on guaranteed event delivery and the high availability of the cloud. |
| Focus on product innovation | Develop richer application scenarios by connecting multiple possible sources and destinations of events. Your business logic can be triggered by virtually all Azure services, as well as custom sources. Fully managed event handling with delivery, intelligent filtering, and the ability to send events to multiple recipients at once allow you to focus on solving business problems rather than infrastructure. |
| Streamline event-driven integration | Integrate workloads hosted on the cloud or Kubernetes using event-driven architectures in Event Grid. Manage Event Grid resources on the cloud or Kubernetes using a single control plane on Azure. Take advantage of hybrid architectures to forward events from Kubernetes to Azure destinations. |
What is Azure Event Grid?
Event Grid is a highly scalable, serverless event broker that you can use to integrate applications using events. Events are delivered by Event Grid to subscriber destinations such as applications, Azure services, or any endpoint to which Event Grid has network access. The source of those events can be other applications, SaaS services and Azure services.
With Event Grid you connect solutions using event-driven architectures. An event-driven architecture uses events to communicate occurrences in system state changes, for example, to other applications or services. You can use filters to route specific events to different endpoints, multicast to multiple endpoints, and make sure your events are reliably delivered.
The event sources and event handlers or destinations are summarized in the following diagram:
Image Processing Example
The following example uses the event-grid on top of the blob-storage to automate image processing when images are added or updated.
SAP Use Case
Inside a S/4HANA or SAP Business Suite ERP system, the SAP Content Server uses Content Repositories supporting storage types to organize file storage. The business case relevant files are synced to an Azure Blog Storage to be linked by a BTP Destination.
The Event Grid is used to link the Azure Blob Storage to an Azure Function as the event source.
Each time a new image is added or updated in a BlogStorage container, a serverless function is triggered to convert the image to the Google WepP file format. The image is also resized for thumbnail and high-quality detail web view.
Blob Storage Event Types
These events are triggered when a client creates, replaces, or deletes a blob by calling Blob REST APIs:
| Event name | Description |
|---|---|
| Microsoft.Storage.BlobCreated | Triggered when a blob is created or replaced. |
| Microsoft.Storage.BlobDeleted | Triggered when a blob is deleted. |
Event triggers an Azure FunctionImage Processing Function