Design an event-driven system
Design domain events, producers, consumers, and an event schema with a justified message broker choice. Covers idempotency, at-least-once delivery, and dead-letter queues.
Preview
Copy prompt
Design an event-driven architecture for [System Description]. Define the key domain events, their producers and consumers, and a concrete event schema with versioning strategy. Recommend a message broker such as Kafka, RabbitMQ, or SQS and justify the choice against the alternatives. Describe how to handle at-least-once delivery guarantees, idempotency at the consumer side, and dead-letter queue strategy for failed events.
More
Architecture
Prompts
