microservices-design
Installation
SKILL.md
Microservices Design
Service Boundaries
Define services around business capabilities, not technical layers. Each service owns its data store and exposes a clear API contract.
order-service/ -> owns orders table, publishes OrderCreated events
inventory-service/ -> owns inventory table, subscribes to OrderCreated
payment-service/ -> owns payments table, handles payment processing
notification-service -> stateless, subscribes to events, sends emails/SMS
Event-Driven Communication
Related skills
More from rohitg00/awesome-claude-code-toolkit
devops-automation
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
116react-patterns
React 19 patterns including Server Components, Actions, Suspense, hooks, and component composition
88database-optimization
Query optimization, indexing strategies, and database performance tuning for PostgreSQL and MySQL
85api-design-patterns
REST API design with resource naming, pagination, versioning, and OpenAPI spec generation
81redis-patterns
Redis patterns including caching strategies, pub/sub, streams for event processing, Lua scripts, and data structures
79frontend-excellence
Modern frontend patterns for React Server Components, performance optimization, and Core Web Vitals
79