HATEOAS na Richardson Maturity Model ni nini?

Question

IT Interview Practice · Accepted Answer

**Richardson Maturity Model (RMM)** hupanga daraja jinsi API ilivyo "RESTful" katika viwango vinne, na **HATEOAS** ni kiwango cha juu zaidi — sharti ambalo watu wengi huliruka.

## Viwango vinne

```text
Level 0 — "The Swamp of POX": one URI, one method (RPC over HTTP).
          POST /api  { "action": "getUser", "id": 42 }
Level 1 — Resources: many URIs, but still one verb.
          POST /users/42  ,  POST /users/42/delete
Level 2 — HTTP Verbs: proper methods + status codes (where most "REST" APIs live).
          GET /users/42 → 200 ,  DELETE /users/42 → 204
Level 3 — Hypermedia Controls (HATEOAS): responses link to what you can do next.
```

API nyingi za "REST" za production ziko **Level 2** — resources, methods, na status codes sahihi. Kwa kawaida hilo ni la kutosha, na ni lengo lenye mantiki kabisa.

## HATEOAS (Level 3)

**HATEOAS** = *Hypermedia As The Engine Of Application State*. Wazo: response hujumuisha **links** zinazomwambia client hatua zipi zinapatikana baadaye, ili client ipite katika API kwa kufuata links badala ya ku-hardcode URLs — kama binadamu anayefuata links kwenye ukurasa wa wavuti badala ya kukariri kila URL.

```http
GET /orders/1001 HTTP/1.1
```
```http
HTTP/1.1 200 OK
Content-Type: application/json

{
  "id": 1001,
  "status": "pending",
  "total": 250,
  "_links": {
    "self":   { "href": "/orders/1001" },
    "pay":    { "href": "/orders/1001/payment", "method": "POST" },
    "cancel": { "href": "/orders/1001/cancel",  "method": "POST" }
  }
}
```

Kwa sababu order iko `pending`, server hutoa links za `pay` na `cancel`. Mara ikilipwa, links hizo hutoweka na link ya `refund` inaweza kutokea — **server huendesha mabadiliko ya hali**, na client hufuata tu links zozote inazopewa.

## Kwa nini ni nadra

Ahadi ni decoupling: clients hazi-hardcode URLs, hivyo server inaweza kuzipanga upya kwa uhuru. Kivitendo clients nyingi hu-hardcode hata hivyo, HATEOAS huongeza utata halisi, na miundo haikuwahi kusawazishwa kikamilifu (HAL, JSON:API, Siren zote hushindana). Faida mara chache huhalalisha gharama.

## Kwa nini ni muhimu

Hili ni swali la kawaida la kiwango cha senior kwa sababu hutenganisha watu **wanaoelewa REST kama ilivyofafanuliwa awali** na wale wanaotumia "REST" kwa ulegevu kumaanisha "JSON juu ya HTTP." Utambuzi wa thamani si kukariri viwango vinne — ni busara ya kusema kwamba **Level 2 ndio kituo tamu cha kivitendo** huku ukijua kwamba REST halisi (ufafanuzi wa Fielding) *unahitaji* HATEOAS, na kuweza kueleza *kwa nini sekta kwa kiasi kikubwa huipuuza*: faida ya decoupling ni halisi lakini mara chache hutimizwa kwa sababu clients hu-hardcode URLs hata hivyo, na utata ulioongezwa pamoja na miundo ya hypermedia inayoshindana hazilipi kwa APIs za kawaida. Kuonyesha unajua HATEOAS *ni nini*, kuweza kuonyesha mfano halisi wa links zinazoendeshwa na hali, na kuweza kubishana kwa uaminifu kuhusu gharama/faida — badala ya kusisitiza kidogma kwamba kila API lazima iwe Level 3 — ndiyo hasa busara iliyosawazishwa, yenye msingi wa uzoefu ambayo wahoji wanaichunguza.

Viwango vinne

HATEOAS (Level 3)

Kwa nini ni nadra

Kwa nini ni muhimu

Maswali yanayohusiana