serverpod-server-events

To coordinate realtime events across Serverpod clusters, publish typed, serializable event models to named channels. Enabling global delivery uses Redis to propagate messages and ensure state changes reach all connected servers.

Pub/sub messaging with typed Dart models works by posting serializable event types to named channels. Consumers then receive these structured realtime updates via reactive streams or callback listeners.

You need Redis for realtime Dart streams when requesting global delivery to share messages across distributed server instances. Local delivery works by default, but cross-server state propagation requires Redis-backed delivery.

The best way to broadcast state changes is publishing a typed event model to a named channel. Consumers can listen via streams or callbacks, receiving updates locally or globally across clusters using Redis.

Yes, you can consume Serverpod events as a reactive stream. The system supports both stream-based consumption and callback listeners for receiving realtime updates from named channels.

Yes, you must define serializable event types before using this Skill. Typed models are required to publish and consume realtime messages safely across named channels and distributed deployments.