WebSocket Scaling Sticky Session Language Collocations
Practise the standard verbs for scaling WebSocket connections with sticky sessions.
0 / 5 completed
1 / 5
Fill in: 'We ___ sticky sessions at the load balancer so a client's WebSocket connection always lands back on the same backend.'
We 'enable' sticky sessions — the standard, established load-balancing collocation for pinning a client to one backend. The other options aren't the recognised term here.
2 / 5
Fill in: 'Relying on sticky sessions alone without a shared state store can ___ a reconnecting client losing all in-memory session data.'
We say pure stickiness will 'leave' state lost on reconnect — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ connection state in a shared Redis store instead of only in a single server's memory, so any backend can serve a reconnect.'
We 'store state' — the standard, simple collocation for persisting connection data in a shared backend. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ open connections evenly across backend instances so one node doesn't end up holding far more sockets than the rest.'
We 'distribute' connections — the standard, simple collocation for spreading load across instances. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the number of concurrent connections per backend closely so scaling decisions are based on real socket counts, not guesses.'
We 'monitor' a count — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.