The main issue that happens with both REST and GraphQL, is that people spend more time thinking of how to implement their thing, than what the API should be. T

The main issue that happens with both REST and GraphQL, is that people spend more time thinking of how to implement their thing, than what the API should be. The complexity GraphQL adds _can_ be worth it for its ability to better represent a business domain via an API. If you don’t care how well your API represents your business domain, then likely your API is going to suck, and you might as well have a sucky REST api and avoid the complexities of GQL.