Azure Fluid Relay
Managed Fluid Framework service that sequences and broadcasts client operations for collaborative editing.
- Provider
- azure
- Category
- Edge
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| ackIntervalSeconds | integer | — | no | — | inherited |
| autoscaling | boolean | — | no | false | inherited |
| channelAssignment | enum | random | hash | sticky | no | random | inherited |
| customerManagedKeys | boolean | — | no | false | inherited |
| drainOnScaleIn | boolean | — | no | false | inherited |
| encryptionAtRest | boolean | — | no | true | inherited |
| managed | boolean | — | no | false | ▸ true |
| protocol | enum | websocket | sse | long-poll | grpc-stream | udp-multicast | no | websocket | ▸ websocket |
| pushFallback | boolean | — | no | false | inherited |
| sequenceNumbers | boolean | — | no | false | ▸ true |
| serverSideCode | 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: "fluid-relay", component: "azure-fluid-relay" }# yaml-language-server: $schema=../../schema/component.schema.json # Azure Fluid Relay: managed Fluid Framework service that takes in client data operations, sequences # them and broadcasts the sequenced operations back, so every client rebuilds the same state. # Encryption at rest is on by default with Microsoft-managed keys. Facts from "Azure Fluid Relay # overview" and "Data encryption in Azure Fluid Relay". schemaVersion: "1" type: "component" id: "azure-fluid-relay" kind: "realtime-gateway" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/azure-fluid-relay/overview/overview" defaults: managed: true protocol: "websocket" stateful: true sequenceNumbers: true properties: encryptionAtRest: type: "boolean" default: true customerManagedKeys: type: "boolean" default: false serverSideCode: type: "boolean" default: false