GraphQL

Single endpoint, client specifies exactly the fields it needs — avoids over/under-fetching on complex nested reads.

Why we need this / what value this brings

Lets the client ask for exactly the fields it needs in one round trip, avoiding both over-fetching and the N+1-requests problem of REST for nested data.

When to use this

Read-heavy, deeply nested data (a storefront page combining service + provider + reviews) with varied client needs.

How to use or implement this

Define a schema, resolvers per field/type, and watch for the N+1 query problem at the resolver level (use dataloaders).

Research questions

• Would a storefront browsing page (services + provider + reviews in one view) benefit from GraphQL over multiple REST calls?

---

Empty folder — drop notes, links, and findings here as you research.