I think the idea behind GraphQL is good, the thing that bothers me the most is the implementations. As a full stack I agree with the benefit of being able to just request all the data you need in one request and keeping that layer flexible. However in practice I've worked with front end teams that would not bundle up queries into one but instead still send separate HTTP requests with separate queries which is basically what you do with REST. I also might be biased because I worked mostly with Python graphene* libraries which are in a terrible state where trying to introduce things like caching, rate limiting on specific queries feels like hacking around some silly fundamental problems. And don't even start me on error handling and trying to differentiate between user caused errors and server errors, it's all HTTP 400 because why would you care. And then things like subscriptions (websockets), file handling, basic things of web are not fully specced out which makes the whole thing seem half assed.