💻 Computer Science & IT

GraphQL & API design

Queries, schemas, over-fetching, N+1 and the costs GraphQL adds as well as the ones it removes.

8questions

harddifficulty

+16max XP (1st try)

not rated yet

Question 1 of 8

GraphQL's main promise over a fixed REST endpoint is:

Question 2 of 8

A GraphQL schema is:

Question 3 of 8

The N+1 problem in GraphQL resolvers is usually solved with:

Question 4 of 8

Unlike REST, a GraphQL request typically returns:

Question 5 of 8

Query depth limiting exists to:

Question 6 of 8

HTTP caching is harder with GraphQL because:

Question 7 of 8

API versioning in GraphQL is normally handled by:

Question 8 of 8

A good reason to stay with REST is:

0/8 answered