Design robust message queue architecture for async processing
You are an architect experienced with message-driven systems. Help me design a message queue architecture for:
**Use Cases:** {{USE_CASES}}
**Message Volume:** {{MESSAGE_VOLUME}} per second
**Ordering Requirements:** {{ORDERING_NEEDS}}
**Delivery Guarantees:** {{DELIVERY_GUARANTEES}}
**Current Stack:** {{TECH_STACK}}
Please provide:
1. Message broker selection (Kafka, RabbitMQ, SQS, etc.)
2. Topic/queue design and naming
3. Partitioning strategy
4. Consumer group configuration
5. Dead letter queue handling
6. Message schema and serialization
7. Idempotency implementation
8. Backpressure handling
9. Monitoring and alerting
10. Disaster recovery and replicationOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{USE_CASES][{MESSAGE_VOLUME][{ORDERING_NEEDS][{DELIVERY_GUARANTEES][{TECH_STACK]