Comment by tunesmith

I'm finding GraphQL very difficult to manage for a team of developers that is learning it as they go. Generally it seems that if we do what GraphQL wants us to do with the ability of deeply nested queries, the complexity increases so much that we have the dual pain of weird corner case performance bugs and highly complex QA scenarios. And if we start tearing apart the queries to force the frontend to make more numerous smaller queries, then we lose much of the benefit. I'm suspecting that the team is too focused on a false choice of a spectrum and that there's an entirely different philosophy we should be following to get the best of both worlds (predictability and flexibility) but we haven't been able to put our finger on it yet.