Review event-driven implementations for message delivery guarantees, idempotent consumers, event schema evolution, and saga pattern correctness.
## CONTEXT Event-driven architectures enable decoupled, scalable systems — but they introduce failure modes that do not exist in synchronous systems. Messages are delivered at-least-once (meaning duplicates), events arrive out of order, consumers crash mid-processing, and schema changes break downstream consumers.…
Premium Prompt
Unlock this prompt — and all 30,000+ expert-crafted prompts — with Pro.
Unlock with Pro