ASP.NET Core SignalR
Self-hosted realtime hub with WebSocket, SSE and long-polling fallback.
- Provider
- default
- Category
- Edge
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| ackIntervalSeconds | integer | — | no | — | inherited |
| autoscaling | boolean | — | no | false | ▸ false |
| backplane | enum | none | redis | azure-signalr-service | no | none | inherited |
| channelAssignment | enum | random | hash | sticky | no | random | ▸ sticky |
| drainOnScaleIn | boolean | — | no | false | inherited |
| hubProtocol | enum | json | messagepack | no | json | inherited |
| managed | boolean | — | no | false | ▸ false |
| 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 |
| stickySessionsRequired | boolean | — | no | true | inherited |
| subscriptionsPerUser | integer | — | no | — | inherited |
| transportFallback | 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.
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: "signalr", component: "signalr" }# yaml-language-server: $schema=../../schema/component.schema.json # ASP.NET Core SignalR, self-hosted in your own app. "Overview of ASP.NET Core SignalR" gives the # transport fallback order WebSockets, Server-Sent Events, long polling with JSON as the default hub # protocol; "Production hosting and scaling" states the same server must handle every request of a # connection, so sticky sessions are required on a farm unless a backplane service is used. schemaVersion: "1" type: "component" id: "signalr" kind: "realtime-gateway" provider: "default" docs: "https://learn.microsoft.com/en-us/aspnet/core/signalr/scale" defaults: protocol: "websocket" stateful: true autoscaling: false channelAssignment: "sticky" managed: false properties: transportFallback: type: "boolean" default: true stickySessionsRequired: type: "boolean" default: true hubProtocol: type: "enum" values: ["json", "messagepack"] default: "json" backplane: type: "enum" values: ["none", "redis", "azure-signalr-service"] default: "none"