Skip to main content

Redis Streams consumers

shared-redis provides RedisStreamConsumerSupport and IntegrationEventConsumerSupport. Each listener declares a stream key and a consumer group.

Operating rules:

  • Group name is configuration, stable per service and event.
  • Pending entries are the first place to look when a projection is stale.
  • STREAMS is the runtime transport. Pub/Sub toggles remain in history for rollback described in ADR 0003; do not turn them on unless you are executing that rollback.
  • Trim uses SHARED_EVENTS_STREAM_MAXLEN. Do not trim below a horizon you have not consumed.

Messaging also uses Redis pub/sub for live WebSocket fan-out. That channel is ephemeral and is not the integration outbox. Chat history is the Postgres row.