GraphQL iku basa query kanggo API lan uga runtime sing mangsuli query kasebut adhedhasar schema sing wis diketik. Klien ngirim siji request sing njlentrehake persis field-field sing dikarepake, banjur server mbalekake persis wangun kuwi — ora luwih, ora kurang.
/users, /users/1/posts); GraphQL mung ngetokake siji endpoint /graphql lan kowe milih data nganggo isi query.# 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
}
}
}
Respons kasebut persis kaya query: { "data": { "user": { "name": "...", "posts": [{ "title": "..." }] } } }.
Pewawancara takon iki kanggo ndeleng apa kowe ngerti trade-off inti-ne: GraphQL ngilangi over/under-fetching lan menehi keluwesan marang klien, nanging kanthi rega kerumitan luwih akeh ing sisih server (resolver, caching, kontrol biaya query). Ngerti kenapa iki ana — ora mung sintakse — nuduhake yen kowe bisa milih piranti sing pas.
Pustaka pitakon wawancara IT kanthi jawaban rinci — saka Junior nganti Senior.
Nyumbang