The article starts with: > With GraphQL, the client speaks a request language which: 1) eliminates the need for the server to hardcode the shape or size of the

The article starts with: > With GraphQL, the client speaks a request language which: 1) eliminates the need for the server to hardcode the shape or size of the data And then ends with: > There are some mitigations we can do here. We can do cost analysis on the query in advance and enforce some kind of limits on the amount of data one can consume. ... so basically you did nothing in the way of perf but add complexity.