Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
11 results across 1 active filter
Page 1 of 1
Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.
Explains why message handlers must tolerate duplicate delivery and how idempotency protects side effects.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Explains retry strategy for transient failures and poison-message handling for permanent failures.
Explains how consumer groups share event-stream work and how offset commits affect duplicate or lost processing.
Explains why exactly-once claims do not remove the need for idempotent side effects and consistency boundaries.
Keeps long-running queue work safe when message ownership expires, renewal fails, settlement is uncertain, or another worker receives the same job.
Preserves order only within the business key that requires it, while handling hot keys, gaps, stale events, replay, and poison messages explicitly.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Makes consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.