Event Grid
Definition
Azure event routing service that connects event sources to event handlers, enabling real-time event-driven architectures and automation.
Use Cases
- Adobe: Automating creative asset workflows when files are added or updated in cloud storage — Uses event-driven patterns on Azure where storage events publish notifications that trigger downstream processing (such as serverless functions) and workflow steps for indexing, transformation, and notifications. (Faster, more reliable automation of file-driven workflows and reduced manual coordination between systems.)
- Heathrow Airport: Operational event notifications for airport systems to improve responsiveness — Implements event-driven integration on Azure, using native event routing to fan out operational events to multiple handlers (for alerting, dashboards, and automated actions) without tightly coupling producers and consumers. (Improved operational visibility and quicker reaction to changes by distributing events in near real time.)
Provider Equivalents
- AWS: Amazon EventBridge
- Azure: Azure Event Grid
- GCP: Eventarc
- OCI: OCI Events
Frequently Asked Questions
- What's the difference between Azure Event Grid and Azure Service Bus?
- Event Grid is for event notifications ("something happened"), optimized for pushing events from many Azure services to handlers with filtering and fan-out. Service Bus is a message broker for commands and reliable messaging between applications ("do this"), with features like queues/topics, message sessions, and more explicit sender/receiver coordination. Use Event Grid for reactive integrations; use Service Bus when you need durable messaging, ordering patterns, or complex messaging workflows.
- When should I use Event Grid?
- Use Event Grid when you want to react to events from Azure services or your own apps—like blob created, resource changed, or custom business events—and route them to multiple consumers (Functions, Logic Apps, Webhooks, Service Bus, etc.). It’s a good fit for loosely coupled architectures, fan-out notifications, and lightweight event-driven automation. If you need long-running workflows, consider pairing it with Logic Apps or Durable Functions; if you need command-style messaging with advanced broker features, consider Service Bus.
- How much does Event Grid cost?
- Event Grid pricing is primarily based on the number of operations (such as event deliveries and management operations). Costs increase with higher event volume, advanced features you enable (for example, certain delivery options), and any downstream services you trigger (Functions, Logic Apps, Service Bus, etc.). For accurate numbers, estimate monthly event count and review the current Azure Event Grid pricing page for your region.
Category: communication
Difficulty: intermediate
Related Terms
See Also