The thing that bothers me about GraphQL is that it adds multiple layers that I have to debug if something goes wrong. I have an app that displays a hello world

The thing that bothers me about GraphQL is that it adds multiple layers that I have to debug if something goes wrong. I have an app that displays a hello world from the server, and it's not displaying, where is the problem? Is it in my UI code? is it in Relay? is it in the server side part of GraphQL? is it in my actual API that returns hello world? If I'm using a good MVC framework on a the backend, I most likely model my schema already in some way, having to duplicate that same information for GraphQL feels wrong. GraphQL fixes the over-fetching problem, however it requires me to implement a server side component for this, that makes me think if it would be less effort to just refine the server side endpoints and not having to support an extra service.