serverpod-server-events

What problem does it solve?

Serverpod developers need a reliable way to publish and consume typed events so that realtime features can coordinate state changes without tightly coupling components.

Core Features & Use Cases

• Post messages on named channels: Send typed, serializable event models to interested consumers.
• Consume events via streams or listeners: Receive updates either as a reactive stream or via callback listeners.
• Local vs global delivery: Use local delivery by default, and enable global (cross-server) messaging through Redis when shared delivery is required.

Use case: You have a multi-server realtime app where user profile changes must notify all connected clients; post a UserUpdate event to a channel locally, or publish globally with Redis so every server instance can react.

Quick Start

Tell the AI to publish a UserUpdate to the user_updates channel using local delivery, then create a stream listener that prints each received message.