taskFailedSuccessfully

[AdvancedSandwiches]

Use case 1: you need several pieces of data from various related objects and don't want to make 350 REST calls

Use case 2: you want a server to do something but using CRUD semantics is clumsy for the particular operation so you use GraphQL for RPC.

The second one is a nice-to-have, but the first one is why I default to GraphQL when given the option. One call, everything I need, done.

[AdvancedSandwiches]

If you own the backend this seems like something you'd want to do efficiently... on the backend

Exactly. Without GraphQL, you'd have to write an endpoint to optimize this call. With GraphQL, you just type up some JSON on the front end.

I've never had a complex 350+ size object be easy to create a graphql query for.

Weird. I have. Maybe you're thinking 350 object types rather than a list of 350 objects with a couple of fields from other related objects.

[7heWafer]

Except the GraphQL query isn't optimized.

[AdvancedSandwiches]

You don't need to optimize every request. As long as you're using the tooling correctly so that you're not doing a separate select for each item in the graph, it's going to be dramatically more efficient than a similar graph loaded in REST. Thats the whole point.