3 ms·

> On the flip side, I've never been frustrated by getting too many fields back from an API A pretty common use-case I have is needing to support these three th

by n_e 6y ago

> On the flip side, I've never been frustrated by getting too many fields back from an API A pretty common use-case I have is needing to support these three things : - A “big object” list screen (where retrieving the whole objects would make the query return megabytes off data) - A “big object” details screen (where I need the full object) - Programmatically getting many big objects With GraphQL it involves writing one (or two) straightforward queries, while with REST it would require more thought or code.

criddell 6y ago
> With GraphQL it involves writing one (or two) straightforward queries, while with REST it would require more thought or code. Aren't you just pushing the work to the back end? The GraphQL resolver is a new layer of complexity while with REST is more straightforward.
- nojvek 6y ago
  Yes, but you don’t have that many network round trips.
  - criddell 6y ago
    Maybe, maybe not. If there is some sequence that is used a lot and you've determined it to be a bottleneck, you can write a custom endpoint for it.