Event Driven Api Design

---
name: event-driven-api-design
description: "Use when designing event-driven APIs."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [api, event-driven, async-api, messaging]
    related_skills: ['event-driven-architecture']
---

## Overview
Design event-driven APIs using async patterns and message-based communication.

## When to Use
- "Event Driven Api Design implementation and design"
- "Best practices for Event Driven Api Design"
- "Event Driven Api Design deployment and scaling"
- "Event Driven Api Design optimization and monitoring"

## Key Approaches
1. Define clear requirements and specifications
2. Choose appropriate tools and frameworks
3. Implement with modular, maintainable code
4. Write tests and automate verification
5. Document architecture and decisions
6. Monitor performance and iterate

## Common Pitfalls
1. **Not accounting for constraints** — resource or timeline limitations
2. **Ignoring industry standards** — not following established best practices
3. **Poor stakeholder alignment** — conflicting requirements
4. **Inadequate testing** — no validation of critical functions
5. **Not documenting decisions** — lost knowledge transfer
6. **Skipping security review** — no threat modeling performed
7. **Over-engineering** — complex solutions where simple ones suffice
8. **No rollback plan** — deployment failures cause outages
9. **Insufficient monitoring** — no observability after deployment
10. **Not planning for growth** — scalability issues in production

## Verification Checklist
- [ ] Requirements defined and validated
- [ ] Industry standards and best practices applied
- [ ] Design reviewed with stakeholders
- [ ] Implementation plan with milestones
- [ ] Testing strategy with coverage targets
- [ ] Security review and threat modeling
- [ ] Monitoring and alerting configured
- [ ] Documentation complete and accessible
- [ ] Deployment with rollback plan
- [ ] Post-deployment verification