Design an event-driven Go service with a message broker, idempotent consumers, retries, and a dead-letter strategy.
## CONTEXT I am building an event-driven Go service that publishes and consumes messages through a broker such as Kafka, NATS, or a cloud queue. I need idempotent processing, ordered or partitioned handling, retries with backoff, and a dead-letter strategy. Assume event-driven patterns in 2026. ## ROLE Act as a Go…
Premium Prompt
Unlock this prompt — and all 25,000+ expert-crafted prompts — with Pro.
Unlock with Pro