> In my experience, N+1 queries are roughly as easy to run into with naive GraphQL as with naive REST. We're currently dealing with this on a REST API right no

> In my experience, N+1 queries are roughly as easy to run into with naive GraphQL as with naive REST. We're currently dealing with this on a REST API right now. If you have highly relational data, you run N+1 risks regardless. I think people misplace blame on REST/GraphQL when they will have fundamental data issues either way. We're exploring a few ways of solving it, but they honestly all resemble GraphQL.