service-mesh
Service Mesh
A Service Mesh is a dedicated infrastructure layer for handling service-to-service communication. It's usually implemented as lightweight network proxies (Sidecars) deployed alongside the application code.
When to Use
- Mature Microservices: You have 20+ services and managing retries, timeouts, and auth in each language is becoming a nightmare.
- Zero Trust Security: You need mTLS (Mutual TLS) between all services.
- Observability: You need uniform metrics (Gold signals) and tracing across a polyglot stack.
Core Concepts
Sidecar Proxy
The mesh injects a proxy (e.g., Envoy) next to your app container. Your app talks to localhost, the proxy handles the network magic.
Control Plane
The brain that configures the proxies (e.g., Istio Control Plane).
More from g1joshi/agent-skills
template
Expert [skill-name] assistance covering [feature 1], [feature 2], and [feature 3]. Use when [working with X], [debugging Y], or [implementing Z].
34mariadb
MariaDB MySQL-compatible database with Galera clustering. Use for MySQL-compatible database needs.
6claude
Anthropic Claude AI models for analysis and coding. Use for AI assistants.
5javascript
JavaScript ES6+ programming including async/await, DOM manipulation, modules, and Node.js. Use for .js files and web development.
4typescript
TypeScript static typing with interfaces, generics, decorators, and type inference. Use for .ts files.
4python
Python programming with type hints, async/await, decorators, and package management. Use for .py files and data science.
4