Kuna tofauti gani kati ya L4 na L7 load balancing, na forward dhidi ya reverse proxies?

Question

IT Interview Practice · Accepted Answer

**Load balancer** husambaza trafiki inayoingia kwenye kundi la servers za backend ili hakuna moja iliyozidiwa na mfumo ubaki upatikanavyo ikiwa server itakufa. Tofauti ya msingi ni *tabaka* linalofanyia kazi:

```text
        L4 (Transport)                        L7 (Application)
  routes by IP + port only            reads HTTP: path, headers, cookies, host
  ┌──────────────┐                    ┌──────────────┐
  │ balancer     │──▶ server A        │ balancer     │  /api/*   ──▶ API pool
  │ (TCP/UDP)    │──▶ server B        │ (HTTP-aware) │  /img/*   ──▶ static pool
  └──────────────┘──▶ server C        └──────────────┘  cookie=X ──▶ sticky backend
  fast, opaque, protocol-agnostic     smart routing, TLS termination, can inspect
```

**L4 load balancing** hufanya kazi kwenye tabaka la Transport: huelekeza muunganisho wa TCP/UDP kulingana na IP na port pekee, bila kuangalia ndani ya packets. Ni ya haraka na rahisi na hufanya kazi kwa protocol yoyote, lakini haiwezi kufanya maamuzi kulingana na maudhui. **L7 load balancing** hufanya kazi kwenye tabaka la Application: hukatisha muunganisho, huchambua HTTP, na inaweza kuelekeza kwa URL path, host, headers, au cookies — ikiwezesha uelekezaji kwa path (`/api` dhidi ya `/static`), sticky sessions, TLS termination, kubanwa, na retries kwa kila request. Gharama ni uchakataji zaidi kwa kila request.

**Proxy** ni mpatanishi, na mwelekeo hufafanua aina:

```text
FORWARD proxy: sits in front of CLIENTS, acts on their behalf (outbound)
   clients ──▶ [forward proxy] ──▶ internet    (corp filtering, caching, anonymity)

REVERSE proxy: sits in front of SERVERS, acts on their behalf (inbound)
   internet ──▶ [reverse proxy] ──▶ backend servers  (LB, TLS, cache, WAF)
```

**Forward proxy** huwakilisha *client* — hukaa kati ya watumiaji na internet kwa filtering, caching, au kuficha utambulisho wa client (corporate proxies, egress kama VPN). **Reverse proxy** huwakilisha *server* — clients hufikiri wanaongea nayo, wakati inasimama mbele ya kundi la backends (nginx, Envoy, edge ya CDN). L7 load balancer *ni* reverse proxy maalum; pia hushughulikia kwa asili TLS termination, caching, rate limiting, na kufanya kazi kama WAF.

## Kwa nini ni muhimu

Load balancers na reverse proxies ni mlango wa kuingia wa karibu kila mfumo unaoweza kupanuka, hivyo wahandisi wa ngazi ya juu hutarajiwa kuwafikiria kwa ufasaha. Maafikiano ya L4 dhidi ya L7 ni uamuzi halisi wa ubunifu — throughput ghafi na kutojali-protocol dhidi ya uelekezaji unaojali maudhui na vipengele — na kuchagua vibaya humaanisha ama balancer bubu ambapo ulihitaji uelekezaji, au kulipa overhead ya L7 ambapo L4 ilitosha. Tofauti ya forward dhidi ya reverse hufafanua majadiliano ya usanifu na hujitokeza mara kwa mara katika mahojiano ya system design, ambapo kukatisha TLS, kuongeza cache, kufanya health checks, na kuwezesha upelekaji bila downtime vyote hutegemea kupata tabaka hili sawa.

Kwa nini ni muhimu

Maswali yanayohusiana