How does GraphQL avoid repeated owner loads?

Goal & mental model verified

API styles expose different contracts. REST centers resources and HTTP semantics; GraphQL executes a schema-selected field graph; gRPC defines RPC services/messages. Spring HATEOAS helps express links and affordances in representations.

Worked example · design exercise synthesis

A broker dashboard asks GraphQL for policies and owners. Request-scoped DataLoader batching can collect owner IDs, reducing repeated lookups without turning the API into one unrestricted database query.

Engineering decision synthesis

Choose REST for familiar interoperable resource APIs, GraphQL for client-shaped graphs, and gRPC for typed RPC requirements. Consider client support, evolution, authorization and observability alongside payload size.

Pitfall & diagnosis synthesis

GraphQL can hide N+1 fetching and expensive query shapes. Changing transport does not supply per-field/resource permissions. Hypermedia links should reflect permitted actions rather than grant authority themselves.

Improve & validate synthesis

Measure query cost and downstream calls. Enforce workload limits and compatible contract evolution; keep authentication, authorization and deadline behavior explicit for each transport.