Stats
Actions
Tags
From fus
Microservices Design and Communication Guide. Covers service design principles, protocol selection, and use cases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fus:backend-microservicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide for microservices architecture and inter-service communication.
Guide for microservices architecture and inter-service communication.
Each service should have:
| Metric | Target |
|---|---|
| Team size | 5-9 people |
| Code size | 10K-50K lines |
| Deployment | < 1 hour |
| Startup time | < 30 seconds |
When to Use:
Protocols:
| Protocol | Use Case | Pros | Cons |
|---|---|---|---|
| REST | CRUD, simple APIs | Ubiquitous, familiar | Over-fetching |
| gRPC | High performance | Fast, type-safe | Learning curve |
| GraphQL | Flexible queries | Client-defined queries | Complexity |
When to Use:
Patterns:
| Pattern | Description |
|---|---|
| Pub/Sub | One-to-many |
| Event Sourcing | State as event log |
| CQRS | Separate read/write |
Need immediate response?
├─ Yes → REST or gRPC
│ └─ High performance? → gRPC
│ └─ Standard CRUD → REST
│
└─ No → Use Message Queue
├─ One-to-many → Pub/Sub
├─ Transactional → Saga
└─ High throughput → Kafka
/resources:
/users:
GET /users # List
POST /users # Create
GET /users/{id} # Read
PUT /users/{id} # Update
DELETE /users/{id} # Delete
service UserService {
rpc GetUser(GetUserRequest) returns (User);
rpc CreateUser(CreateUserRequest) returns (User);
rpc StreamUsers(StreamRequest) returns (stream User);
}
10 services
| Solution | Features | Complexity |
|---|---|---|
| Istio | Full-featured | High |
| Linkerd | Simpler than Istio | Medium |
| Envoy | Data plane | Low |
npx claudepluginhub genuineh/fus --plugin fusGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.