Centrifugo
Self-hosted realtime messaging server over WebSocket, SSE, HTTP-streaming and GRPC.
- Provider
- default
- Category
- Edge
- Official docs
- https://centrifugal.dev/docs/server/engines
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| ackIntervalSeconds | integer | — | no | — | inherited |
| autoscaling | boolean | — | no | false | ▸ false |
| channelAssignment | enum | random | hash | sticky | no | random | inherited |
| drainOnScaleIn | boolean | — | no | false | inherited |
| engine | enum | memory | redis | nats | no | memory | inherited |
| historyPersisted | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ false |
| presence | boolean | — | no | false | inherited |
| protocol | enum | websocket | sse | long-poll | grpc-stream | udp-multicast | no | websocket | ▸ websocket |
| pushFallback | boolean | — | no | false | inherited |
| sequenceNumbers | boolean | — | no | false | inherited |
| stampedeGuard | boolean | — | no | false | inherited |
| stateful | boolean | — | no | true | ▸ true |
| subscriptionsPerUser | integer | — | no | — | 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.
When a gateway holding millions of sockets restarts, every client reconnects at once and the gateway asks the coordination service about each of them. Without a stampede guard that lookup storm takes the coordination service down too.
- — all of these hold:
- — the node has at least one synchronous outgoing edge to a coordination-service
- — the node's `stampedeGuard` is false
With heavy-tail traffic a few channels carry most of the load. Assigning channels at random lands those hot channels on arbitrary hosts, and every tenant sharing a host suffers for it.
- — all of these hold:
- — the node's `channelAssignment` is "random"
- — the design requirement `traffic.skew` is "heavy-tail"
Scaling a gateway down kills every live WebSocket on the removed instance at once. Without a drain step those clients all reconnect together.
- — all of these hold:
- — the node's `autoscaling` is true
- — the node's `drainOnScaleIn` is false
nodes:
- { id: "centrifugo", component: "centrifugo" }# yaml-language-server: $schema=../../schema/component.schema.json # Centrifugo: self-hosted realtime messaging server with WebSocket, SSE, HTTP-streaming, WebTransport # and GRPC transports. "Engines and scalability" states the default engine is `memory`, which runs a # single node only and does not persist channel history between restarts; Redis or Nats are needed to # run several nodes. schemaVersion: "1" type: "component" id: "centrifugo" kind: "realtime-gateway" provider: "default" docs: "https://centrifugal.dev/docs/server/engines" defaults: protocol: "websocket" stateful: true autoscaling: false managed: false properties: engine: type: "enum" values: ["memory", "redis", "nats"] default: "memory" historyPersisted: type: "boolean" default: false presence: type: "boolean" default: false