> That’s not typically the kind of queries a GraphQL execution results in. If anything, naively implemented, GraphQL results in a ton of small queries for every

> That’s not typically the kind of queries a GraphQL execution results in. If anything, naively implemented, GraphQL results in a ton of small queries for every resolver. This seems like mincing words to me. Any SQL programmer worth their salt knows that if you compose "a ton of small queries" into a single query and let the DB engine do its thing the execution time will be lower.