@feld @alex Not really. At least, if you contort a REST API to do what GraphQL can do, it loses the advantages of REST APIs. The singular advantage of a REST API is that they are highly cacheable. The advantage of GraphQL is that it's easier to make querying child objects in a single request, you can add query parameters to a REST API to include specific child objects, but you have to do this specifically for each child object, and it also becomes a new request that can't be cached with the other requests.