Help us improve
Share bugs, ideas, or general feedback.
From system-design
Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.
npx claudepluginhub sethdford/claude-skills --plugin architect-system-designHow this skill is triggered — by the user, by Claude, or both
Slash command
/system-design:service-mesh-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Apply service mesh patterns (Istio, Linkerd) to decouple service communication from business logic, enabling uniform resilience and observability.
Architects service meshes using Istio and Linkerd for Kubernetes, covering traffic management, mTLS security, observability, multi-cluster federation, and canary deployments.
Configures Istio, Linkerd, and Consul Connect for Kubernetes microservices. Generates mTLS, traffic routing, resilience policies, and observability configs.
Deploys and configures Istio or Linkerd service mesh in Kubernetes for secure mTLS communication, traffic management, observability, circuit breaking, and policy enforcement. Use for microservices needing canary deployments or service-level observability.
Share bugs, ideas, or general feedback.
Apply service mesh patterns (Istio, Linkerd) to decouple service communication from business logic, enabling uniform resilience and observability.
You are designing service mesh infrastructure for microservices. The user is dealing with complex service-to-service communication, resilience challenges, or observability gaps. Read their current infrastructure.
Based on Istio/Linkerd reference implementations and distributed systems research:
Assess Mesh Necessity: Service mesh adds complexity. Evaluate: are you managing >10 services? Do you need fine-grained traffic control? Do you have mTLS requirements? If yes to 2+, mesh may help.
Design Sidecar Injection: Configure automatic sidecar injection for namespaces. Specify resource requests (sidecars consume ~10-50MB memory per instance).
Configure Routing & Load Balancing: Define traffic policies (round-robin, least request, random). For canary deployments, specify traffic split (90% stable, 10% canary).
Implement Resilience Policies: For each service-to-service communication, specify:
Enable Observability: Configure telemetry collection. Send metrics to Prometheus, traces to Jaeger. Define dashboards for request latency, error rate, saturation.