Loading
Pick a focused question that fits your time, stack, and interview goal.
8 results across 1 active filter
Page 1 of 1
Explains useful message metadata for tracing, idempotency, ownership, versioning, and support diagnostics.
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 to reprocess event streams safely for new projections, bug fixes, and data repair.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Explains how multiple worker instances share queue work and what limits safe scaling.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.