Menene GraphQL kuma yaya ya bambanta da REST?

Question

IT Interview Practice · Accepted Answer

GraphQL harshe ne na tambaya (query language) don API kuma runtime da yake amsa waɗannan tambayoyi bisa wani schema mai nau'i (typed schema). Abokin ciniki yana aika **buƙata guda ɗaya** da ke bayyana ainihin filayen da yake so, sai uwar garke ta mayar da ainihin siffar da aka nema — ba fiye ba, ba kaɗan ba.

## Yadda ya bambanta da REST

- **Endpoint guda ɗaya maimakon da yawa.** REST yana bayyana URL da yawa (`/users`, `/users/1/posts`); GraphQL yana bayyana endpoint guda ɗaya na `/graphql` kuma kana zaɓar bayanai da jikin tambayar.
- **Abokin ciniki yana zaɓar filayen.** Amsoshin REST an gyara su daga uwar garke, don haka sau da yawa kana samun fiye da kima (over-fetching) ko kaɗan sosai (under-fetching, wanda yake tilasta ƙarin zagayowa). GraphQL yana barin abokin ciniki ya nemi ainihin abin da yake buƙata.
- **Typed schema.** Kowane fili yana da nau'i, don haka kayan aiki za su iya tabbatar da tambayoyi da samar da takardu ta atomatik.

```graphql
# One request fetches a user AND their posts' titles — no second round trip
query {
  user(id: "1") {   # pick the user by id
    name            # only the fields we list come back
    posts {         # nested: follow the relationship in the same query
      title
    }
  }
}
```

Amsar tana yin madubi ga tambayar daidai wa daida: `{ "data": { "user": { "name": "...", "posts": [{ "title": "..." }] } } }`.

## Me ya sa yake da muhimmanci

Masu tambayoyin hira suna yin wannan tambaya don ganin ko ka fahimci **babban ciniki-ciniki**: GraphQL yana kawar da over/under-fetching kuma yana ba abokan ciniki sassauci, a kan tsadar ƙarin rikitarwa a gefen uwar garke (resolvers, caching, sarrafa tsadar tambaya). Sanin *dalilin* da ya sa yake wanzuwa — ba kawai tsarin rubutu ba — yana nuna cewa za ka iya zaɓar kayan aiki daidai.

Yadda ya bambanta da REST

Me ya sa yake da muhimmanci

Tambayoyi masu alaƙa