Topic
At-least-once delivery, idempotency, retries, dead letters, locks, ordering, inbox/outbox, and duplicate handling.
Practice items tagged with Messaging Reliability.
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.