Add the fact that the cache performance is unpredictable and inconsistent. GraphQL queries select specific fields for “performance reasons” so each request is

Add the fact that the cache performance is unpredictable and inconsistent. GraphQL queries select specific fields for “performance reasons” so each request is custom and you can't cache at the edge. This is ridiculous because SQL joins are costly but fetching a few extra textual fields is basically never a bottleneck. So in order to save a few bytes or KBs (which nobody care about anyway), you ruin your caching abilities... ...Well unless you manually cache your GraphQL queries with more fields than needed but then what's the point of using GraphQL at all? That's very often a terrible compromise.