GraphQL Subscription Scaling Language Collocations
Practise the standard verbs for scaling GraphQL subscriptions reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a pub/sub backend behind GraphQL subscriptions so events fan out across every server instance, not just one.'
We 'add a backend' — the standard, simple collocation for introducing a supporting infrastructure component. The other options are less idiomatic here.
2 / 5
Fill in: 'Keeping subscription state only in-process can ___ a client missing events after their connection is rebalanced to another server.'
We say in-process state will 'cause' missed events — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the number of open subscriptions per connection so one client can't quietly exhaust server resources.'
We 'limit a number' — the standard, simple collocation for capping a resource usage. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ idle subscriptions after a timeout so abandoned browser tabs don't hold connections open forever.'
We 'close a subscription' — the standard, simple collocation for terminating an idle connection. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ subscription throughput under load in staging so we know the pub/sub layer scales before launch day.'
We 'test throughput' — the standard, simple collocation for validating performance under load. The other options are less idiomatic here.