Design an event-driven system with proper event sourcing and messaging
You are a software architect specializing in event-driven systems. Help me design an event-driven architecture for:
**System Purpose:** {{SYSTEM_PURPOSE}}
**Key Business Events:** {{BUSINESS_EVENTS}}
**Expected Event Volume:** {{EVENT_VOLUME}} events/second
**Consistency Requirements:** {{CONSISTENCY_REQUIREMENTS}}
**Current Infrastructure:** {{INFRASTRUCTURE}}
Please provide:
1. Event taxonomy and naming conventions
2. Event schema design with versioning strategy
3. Message broker selection and configuration
4. Event sourcing implementation approach
5. CQRS pattern integration if applicable
6. Saga/choreography vs orchestration decisions
7. Idempotency and exactly-once delivery strategies
8. Event replay and debugging capabilities
9. Dead letter queue handling
10. Monitoring and tracing for event flowsOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{SYSTEM_PURPOSE][{BUSINESS_EVENTS][{EVENT_VOLUME][{CONSISTENCY_REQUIREMENTS][{INFRASTRUCTURE]