3 ms·

https://relay.dev/docs/principles-and-architecture/thinking-in-graphql/ https://relay.dev/docs/principles-and-architecture/thinking-... Take a look at this. Ei

https://relay.dev/docs/principles-and-architecture/thinking-in-graphql/ https://relay.dev/docs/principles-and-architecture/thinking-... Take a look at this. Either you didn't know what's challenging about caching nested graph data, or we have different definitions of triviality/interns.

arinlen 4y ago
> Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my word for it. It's really that bad. https://graphql.org/learn/caching/ https://graphql.org/learn/caching/