Practise the standard verbs for handling Redis pub/sub messaging reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a Redis channel for cross-service notifications, rather than polling a database nobody actually needs to hit that often.'
We 'subscribe to a channel' — the standard, simple collocation for listening on a Redis pub/sub channel. The other options are less idiomatic here.
2 / 5
Fill in: 'A disconnected subscriber with no reconnect logic can ___ published messages dropped silently with nobody actually noticing.'
We say a disconnect will 'leave' messages dropped silently — the standard, natural collocation for the resulting message loss. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a namespaced channel per event type, rather than one broad topic nobody can actually filter cleanly.'
We 'define a channel' — the standard, simple collocation for naming a Redis pub/sub topic. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every publisher's message rate against subscriber throughput, rather than assuming capacity nobody's actually measured.'
We 'check a rate' — the standard, simple collocation for validating pub/sub throughput. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ subscriber lag on a monitoring dashboard, rather than discovering a stuck consumer only once messages are actually backing up.'
We 'monitor lag' — the standard, simple collocation for watching how far behind a subscriber falls. The other options aren't idiomatic here.