microservices-design
Microservices design patterns including service mesh, event-driven architecture, saga pattern, and API gateway
Profile →npx skills add rohitg00/awesome-claude-code-toolkit --skill microservices-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```typescript interface DomainEvent { eventId: string; eventType: string; aggregateId: string; timestamp: string; version: number; payload: Record<string, unknown>; } const orderCreatedEvent: DomainEvent = { eventId: crypto.randomUUID(), eventType: "order.created", aggregateId: orderId, timestamp: new Date().toISOString(), version: 1, payload: { customerId, items, totalAmount }, }; await broker.publish("orders", orderCreatedEvent); ``` ```typescript async function handleOrderCreated(event: DomainEvent) { const { items } = event.payload as OrderPayload; for (const item of items) { await db.inventory.update({ where: { productId: item.productId }, data: { quantity: { decrement: item.quantity } },
- Service Boundaries
- Event-Driven Communication
- Saga Pattern (Orchestration)
- API Gateway Pattern
- Health Check Pattern
- Anti-Patterns
- Checklist
What does the microservices-design skill do?
Microservices design patterns including service mesh, event-driven architecture, saga pattern, and API gateway
How do I install it?
Run `npx skills add rohitg00/awesome-claude-code-toolkit --skill microservices-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/awesome-claude-code-toolkit, a repository with 2,438 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.