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 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 how to reprocess event streams safely for new projections, bug fixes, and data repair.
Explains command messages versus event messages and how ownership changes their design.
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.
Explains operational signals for queue-backed systems and how to respond when consumers fall behind.
Preserves order only within the business key that requires it, while handling hot keys, gaps, stale events, replay, and poison messages explicitly.
Chooses event retention and compaction from consumer outage, replay, rebuild, audit, and disaster-recovery requirements rather than storage cost alone.
Explains event schema evolution, backward compatibility, additive changes, consumer rollout, and contract ownership.