A webhook sender cannot distinguish a lost success response from a failed request, so delivery may repeat. Build one durable business effect with identity, signatures, inbox claims, and recovery.
Historical replay should rebuild state without repeating real-world effects. Separate projections from effectors and give every intended notification, payment, or command a durable identity.
When arrival rate exceeds processing capacity, pressure becomes producer delay, broker lag, memory, disk, rejection, or data loss. Choose the boundary and bound it explicitly.
A Kafka rebalance can revoke a partition while application work is still running. Track ownership generations, contiguous completion, offset commits, and external effects explicitly.
A saga cannot rewind remote history. Each compensation is a new, fallible business operation with its own identity, policy, evidence, and possible manual outcome.