4 ms·
> My coworker found a GraphQL query only about five layers deep that could tip over a service. I find arguments like this a bit odd. That's a pretty deep query
by SkyPuncher 3y ago
> My coworker found a GraphQL query only about five layers deep that could tip over a service.
I find arguments like this a bit odd. That's a pretty deep query in REST as well.
I don't have extensive experience with GraphQL, but the complaints I see about it often seem like things you just shouldn't be doing anyways - or, if you do, they're going to be rough in REST as well.
- anttiviljami 3y agoI think the point is, graphql apis tend to be so flexible that it’s easy to accidentally ship an API that allows clients to craft excessively heavy nested queries in a single request. Supporting nested queries isn’t really a common thing in REST, and it’s simpler to rate limit clients by resource than query complexity.