Loading
Pick a focused question that fits your time, stack, and interview goal.
7 results across 1 active filter
Page 1 of 1
Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.
Explains how to reprocess event streams safely for new projections, bug fixes, and data repair.
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.
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.