I know about apollo caching, but it's strictly inferior to HTTP caching which has tons of options (Vary, Etag, etc) Caching per user is still going to mean ton

I know about apollo caching, but it's strictly inferior to HTTP caching which has tons of options (Vary, Etag, etc) Caching per user is still going to mean tons of cache misses. Caching based on the query hash means you're going to cache subsets of the same data over and over as separate entries. With resources over HTTP, you can separate the user specific part from the generic resource part and cache accordingly. Plus, I like the option of caching somewhere else than the app server, like a distributed Varnish. I'm not saying you can't cache with graphQL, it's just less natural and mature.