Several subscribers should react to custom events, and each wants only some event types. Which service is built for this?
Why D is the answer
Azure Event Grid with filters
Event Grid routes events to handlers and supports filtering and retries. It is built for reacting to events, while Service Bus is built for durable work queues.
In detail
- Event Grid routes events to many subscribers.
- Filters let each one pick event types.
- Events announce something happened.
Use case
An illustrative scenario, not a real incident.
A shop publishes order events. Billing subscribes to one type and email to another, each with an Event Grid filter.
See it in different ways
flowchart TD
A{"What are you sending?"} -->|"A notification about a change"| B["Event Grid"]
A -->|"Work that must be processed reliably"| C["Service Bus"]
C --> D["Queue: one consumer per message"]
C --> E["Topic: many subscribers"]mindmap
root((Messaging))
Event Grid
Events
Filters
Service Bus queue
One worker per message
Service Bus topic
Many subscribers
Own filters
Dead-letter queue
Failed messagessequenceDiagram participant P0 as Publisher participant P1 as Event Grid participant P2 as Billing participant P3 as Email P0->>P1: Custom event P1->>P2: Payment events P1->>P3: Signup events
Key point: Event Grid routes filtered events.
Why the other options are wrong
- A. Azure Cosmos DB with the change feed
- The change feed reacts to database changes.
- B. Azure Container Registry with webhooks
- Webhooks there are about registry events.
- C. Azure App Configuration with refresh
- App Configuration holds settings.