Redis Pub/Sub
Pub/Sub topicredis-pubsub
Fire-and-forget channel fan-out inside Redis; disconnected subscribers miss messages.
- Provider
- default
- Kind
- Pub/Sub topic
- Category
- Messaging
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| cluster | boolean | — | no | false | inherited |
| delivery | enum | at-most-once | at-least-once | exactly-once | yes | — | ▸ at-most-once |
| managed | boolean | — | no | false | inherited |
| ordering | enum | none | per-key | no | none | ▸ per-key |
| 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: "redis-pubsub", component: "redis-pubsub" }EventBridgealibaba-eventbridgeAmazon EventBridgeaws-eventbridgeAmazon SNSsnsAzure Event Gridazure-event-gridAzure Event Grid MQTT Brokerazure-event-grid-mqttEclipse MosquittomosquittoMQTT brokermqtt-brokerNanoMQnanomqGeneric Pub/Sub topicpubsub-topicEventarcgoogle-eventarcGoogle Cloud Pub/Subgoogle-pubsubOCI Eventsoci-events
# yaml-language-server: $schema=../../schema/component.schema.json # Redis PUBLISH/SUBSCRIBE: fire-and-forget fan-out. Messages sent while a subscriber is disconnected are lost. schemaVersion: "1" type: "component" id: "redis-pubsub" kind: "pubsub-topic" provider: "default" docs: "https://redis.io/docs/latest/develop/interact/pubsub/" defaults: delivery: "at-most-once" ordering: "per-key" replay: false properties: cluster: type: "boolean" default: false