(Author here) So, I actually mostly agree with you on the dangers. But I also have to ask myself, "is it still a fundamentally better situation?" To me, the ans

(Author here) So, I actually mostly agree with you on the dangers. But I also have to ask myself, "is it still a fundamentally better situation?" To me, the answer is yes. The dangers you point out aren't flaws with the paradigm, but risks for abuse. Completely comparable risks also exist with REST, though. It's going to take time to develop the same level of sophistication in implementation in the GraphQL world. And I think part of the abuse comes from the way the technology is currently taught. A big part of the reason I wrote the article is because I think GraphQL is the future because of what it actually is, rather than the way people commonly think of it. In most situations, I think GraphQL is going to lead to more rational API design, if people focus on modeling the what the client needs to tell the server to do rather than building robust query systems with it (unless that's the first-class need).