Menene service mesh kuma me yasa za ka yi amfani da ita?

Question

Accepted Answer

A **service mesh** (Istio, Linkerd) tsiyon abubuwan sadarwa da ke wuce — retries, timeouts, mTLS, traffic routing, observability — **daga code na app** zuwa layer na gida na sadarwa na **sidecar proxies**.

## Yadda ake aiki

Kwakwalwa kowane instance ina tare da **sidecar proxy** (misali, Envoy). Duk traffic yana wuce ta hanyar proxies, waɗanda ke samar da **data plane**; **control plane** yana saita su.

```text
┌─────────────────┐        ┌─────────────────┐
│ Service A       │        │ Service B       │
│  app  ⇄ [proxy] │◀──────▶│ [proxy] ⇄  app  │
└─────────────────┘  mTLS  └─────────────────┘
        ▲ configured by ▲
        └──── Control Plane (Istio/Linkerd) ────┘
```

## Abin da ake samar

- **mTLS** tsakanin ayyuka ta atomatik (sifili canja app).
- **Resilience** — retries, timeouts, circuit breaking a proxy.
- **Traffic management** — canary, A/B, weighted routing.
- **Observability** — uniform metrics, traces, logs.

## Misalin manufa

```yaml
# shift 10% of traffic to v2 (canary), no code change
route:
  - destination: { host: orders, subset: v1 }
    weight: 90
  - destination: { host: orders, subset: v2 }
    weight: 10
```

## Trade-offs

Mesh yana ƙara latency (hops na kari), rashin kuɗi na albarkatun (proxy ɗaya ga pod), da ainihin rikitaccen gida.

## Me yasa yana da mahimmanci

Mesh yana daidaita resilience, security, da observability a gida duk ayyuka ba tare da kowane ƙungiya ba ta maimaita su a harsuna daban-daban.

Amma tana da nauyi: karɓi ta ne sai da lokacin da za ka sami isassun ayyuka don halayen sadarwa na maimaita su na katako farashi na gida na mesh.