[muffa]

I find it to be more complex(Hence more error prone), less performant, harder to resolve bugs.

For a queries and mutations you still need to write business-logic and database access which is very similar to how you would develop a REST-API.

[praveenweb]

On the performance side, there is definitely the N+1 problem which is solved (partially) by the data loader pattern. But curious if the benefits vs tradeoffs is in favour of GraphQL? And have you considered tools like Hasura/Postgraphile that take care of boilerplate CRUD APIs for databases? Then you actually just focus on writing business logic.

[muffa]

I actually don't use GraphQL in my current position, so I don't think to much about it any more. Intresting tools which I might consider in the future(If I have to write GraphQL).