Microsoft Azure Event Grid
You can use Event Grid, a highly scalable serverless event broker, to integrate applications that use 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 programs, SaaS services, and Azure services may be the source of those occurrences.
Using event-driven architectures, you may connect solutions with Event Grid. An event-driven architecture makes use of events to inform other applications or services, for instance, of changes in the system state. Filters can be used to multicast numerous endpoints, route particular events to distinct endpoints, and ensure that your events are successfully delivered.
Azure Event Grid is set up to spread organically across several fault domains in every region and between availability zones to maximize availability (in regions that support them). The regions that Event Grid supports are listed under "Products available by region."
The following diagram provides a summary of the event sources and event handlers or destinations.
Event sources
The following event sources are supported by Event Grid:
1. A service or product that you offer that publishes events to Event Grid so that users can subscribe to them. Depending on your needs, Event Grid offers two different sorts of resources.
Custom Topics, or just “Topics.” If your needs resemble the following user story, use custom topics:
“As the owner of a system, I want to communicate changes in the state of my system by publishing events and sending them to event handlers that are either under my control or not and can treat my system’s events in any way they see fit.”
Domains. If you wish to scale the delivery of events to too many teams, use domains. Your prerequisites most likely match those listed below:
“As a system owner, I want to notify various teams within a single tenant when the state of my system changes so they can handle its events as they see proper.”
2. With the help of a feature called Partner Events, a SaaS platform or provider can post their events on Event Grid. You could, for instance, automate processes by subscribing to those occurrences. The following partners’ events are currently accessible.
Auth0
API for Microsoft Graph. You can retrieve events from Microsoft Teams, Microsoft Outlook, Azure Active Directory, SharePoint, Conversations, security alerts, and Universal Print using the Microsoft Graph API.
a feature of Azure. Sending events to Event Grid is supported by the following Azure services. Select the link to view additional details about a source in the list.
1. Azure API Management
2. Azure App Configuration
3. Azure App Service
4. Azure Blob Storage
5. Azure Cache for Redis
6. Azure Communication Services
7. Azure Container Registry
8. Azure Event Hubs
9. Azure Health Data Services
10. Azure IoT Hub
11. Azure Key Vault
12. Azure Kubernetes Service
13. Azure Machine Learning
14. Azure Maps
15. Azure Media Services
16. Azure Policy
17. Azure resource groups
18. Azure Service Bus
19. Azure SignalR
20. Azure subscriptions
Event handlers
See event handlers for complete information on each handler’s capabilities and related articles. Webhooks are one of the Azure services that can now handle events from Event Grid. Webhooks are supported by Logic Apps and Azure Automation runbooks.
· Azure functions
· Event Hubs
· Service Bus queues and topics
· Relay hybrid connections
· Storage queues
Concepts
In Azure Event Grid, there are five ideas that will help you get started:
Events — What happened?
Event sources: where the event took place.
The endpoint where publishers send events.
Event subscriptions are the endpoint or built-in mechanism to route events, sometimes to more than one handler. Subscriptions are also used by handlers to intelligently filter incoming events.
Event handlers: the app or service reacting to the event
Capabilities
These are a few of Azure Event Grid’s salient characteristics:
Aim events from your Azure resource to any event handler or endpoint simply by pointing and clicking.
Advanced filtering: To ensure that event handlers only receive pertinent events, filter on event type or event publish path.
To transmit copies of the event to as many locations as necessary, subscribe to several endpoints for the same event using the fan-out technique.
Event delivery is guaranteed by a 24-hour retry with exponential backoff.
Pay-per-event: Only pay when you utilize Event Grid.
Build high-volume workloads on the Event Grid for high throughput.
Built-in Events: Utilize predefined built-in events to get up and running quickly.
Custom Events: To route, filter, and consistently deliver custom events in your app, use Event Grid.
What can I do with Event Grid?
The following features of Azure Event Grid significantly enhance serverless, operations automation, and integration work:
Serverless application architectures
Data sources and event handlers are connected by Event Grid. For instance, when adding images to a blob storage container, utilize Event Grid to start a serverless function that analyzes the images.
Ops Automation
You can expedite automation and make policy enforcement simpler with Event Grid. For instance, you might use Event Grid to alert Azure Automation whenever an Azure SQL virtual machine or database is created. Use the events to add metadata to operations tools, tag virtual machines, check automatically that service configurations are compatible, or file work items.
Application Integration
Your app is connected to other services through Event Grid. For instance, use Event Grid’s dependable delivery, sophisticated routing, and direct interaction with Azure by creating a custom topic to transmit your app’s event data there. Alternatively, you can process data anywhere without writing code by combining Event Grid with Logic Apps.
How much does Event Grid cost?
Due to Azure Event Grid’s pay-per-event pricing structure, you only pay for the services you actually utilize. Every month, the first 100,000 procedures are free. Events entering the system in an attempt to distribute subscriptions, administration calls, and subject suffix filtering are all considered operations.
Use Event Grid to power your event-driven and serverless apps
With Event Grid, a single service for controlling the routing of all events from any source to any destination, you can simplify your event-based systems. Event Grid allows you to concentrate on your app logic rather than infrastructure because it is built for high availability, consistent performance, and dynamic scale.
Feature Of Microsoft Azure Event Grid
Simplify event delivery
Eliminate polling and the delays and costs that come with it. With Event Grid, you can create scalable serverless apps, microservices, and distributed systems because event publishers and event subscribers are separated using a pub/sub approach and straightforward HTTP-based event delivery.
Build reliable cloud applications
Gain a huge, dynamic scale while receiving notifications of changes that are relevant to you almost immediately. Utilize guaranteed event delivery and the cloud’s high level of availability to create smarter, more dependable applications.
Focus on product innovation
Connecting many potential sources and destinations for events can let you create more complex application scenarios. Almost all Azure services, in addition to bespoke sources, can trigger your business logic. You may concentrate on resolving business issues rather than infrastructure issues by using fully managed event handling with delivery, sophisticated filtering, and the capacity to transmit events to many receivers simultaneously.
Streamline event-driven integration
Utilize event-driven architectures in Event Grid to integrate workloads running on Kubernetes or the cloud. Utilize a single Azure control plane to manage Event Grid resources in Kubernetes or the cloud. To route events from Kubernetes to Azure destinations, use hybrid architectures.
Conclusion
You can use Event Grid, a highly scalable serverless event broker, to integrate applications that use events. Events are provided by Event Grid to subscriber destinations like applications, Azure services, or any other endpoint to which Event Grid has network access. Other programs, SaaS services, and Azure services may be the source of those occurrences.
