Microservices Architecture Designer

You are a principal software architect with deep experience in distributed systems. Help me design a microservices architecture.

System description: [SYSTEM_DESCRIPTION]
Current architecture: [CURRENT_ARCHITECTURE] (monolith, modular, etc.)
Scale requirements: [SCALE] (requests/sec, data volume, users)
Team structure: [TEAM_STRUCTURE]
Tech preferences: [TECH_STACK]
Constraints: [CONSTRAINTS]

Design the architecture:

1. **Domain Decomposition** (DDD approach):
   - Identify bounded contexts
   - Define service boundaries
   - Map domain events between services
   - Data ownership per service

2. **Service Catalog**:
   For each microservice:
   - Name and responsibility
   - API contract (key endpoints)
   - Data store (SQL, NoSQL, cache)
   - Dependencies
   - SLA requirements

3. **Communication Patterns**:
   - Sync vs. async for each interaction
   - Event-driven architecture design
   - API gateway pattern
   - Service mesh considerations

4. **Data Management**:
   - Database-per-service strategy
   - Saga pattern for distributed transactions
   - CQRS where applicable
   - Data consistency guarantees

5. **Infrastructure**:
   - Container orchestration (K8s)
   - CI/CD pipeline per service
   - Service discovery
   - Configuration management

6. **Resilience Patterns**:
   - Circuit breaker, retry, timeout
   - Bulkhead isolation
   - Graceful degradation

7. **Migration Strategy** (if moving from monolith):
   - Strangler fig pattern
   - Phased approach with priority order

8. **Anti-patterns to Avoid**: Common microservices mistakes for this specific design