Agree with everything here, but something that often gets missed is that you don't have to use all that GraphQL enables from day one. It is perfectly fine to s

Agree with everything here, but something that often gets missed is that you don't have to use all that GraphQL enables from day one. It is perfectly fine to start with an early implementation that treats GraphQL as mostly an RPC, with only resolvers for Query & Mutation types. You still benefit from GraphQL's type-safety, batching and code-generation. Once you have more familiarity with dataloaders, query complexity etc. update your output objects to have links to other output objects building the graph model. The issue is that too many people get fascinated with GraphQL early, then build deep & complex topologies and expose it in inefficient and potentially insecure way.