Azure Event Grid
Managed push-based event router with 24-hour retry and optional dead-lettering.
- Provider
- azure
- Kind
- Pub/Sub topic
- Category
- Messaging
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| deadLettering | boolean | — | no | false | inherited |
| delivery | enum | at-most-once | at-least-once | exactly-once | yes | — | ▸ at-least-once |
| managed | boolean | — | no | false | ▸ true |
| ordering | enum | none | per-key | no | none | ▸ none |
| replay | boolean | — | no | false | ▸ false |
| topicPerEventType | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
pubsub-replay-required
The design declares that consumers must be able to replay history. A fan-out topic that does not retain messages cannot deliver that.
- — all of these hold:
- — the design requirement `messaging.replay` is true
- — the node's `replay` is false
nodes:
- { id: "event-grid", component: "azure-event-grid" }EventBridgealibaba-eventbridgeAmazon EventBridgeaws-eventbridgeAmazon SNSsnsAzure Event Grid MQTT Brokerazure-event-grid-mqttEclipse MosquittomosquittoMQTT brokermqtt-brokerNanoMQnanomqGeneric Pub/Sub topicpubsub-topicRedis Pub/Subredis-pubsubEventarcgoogle-eventarcGoogle Cloud Pub/Subgoogle-pubsubOCI Eventsoci-events
# yaml-language-server: $schema=../../schema/component.schema.json # Azure Event Grid: push-based event routing, at-least-once with 24 hours of retries; no replay, # dead-lettering to a storage account is opt-in. schemaVersion: "1" type: "component" id: "azure-event-grid" kind: "pubsub-topic" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/event-grid/overview" defaults: managed: true delivery: "at-least-once" ordering: "none" replay: false properties: deadLettering: type: "boolean" default: false