DEV Community

loading...

Discussion on: 4 reasons why you should use GraphQL over REST APIs

Collapse
slavius profile image
Slavius

Out of curiosity, how much dedicated cache storage your typical GraphQL cache server has?

Thread Thread
kfwerf profile image
Kenneth van der Werf

hmnn im not sure, i think caching is mainly handled through its subsidiaries, so cant say to be sure. Bigger issue seems to be fanning out for requests, as one graphql request can potentially mean a lot of subsequent requests fanning out over multiple microservices.

Thread Thread
slavius profile image
Slavius

Statistically as tiny as 5 column table (with 4 really usable columns as one of them is typically an identifier) has 120 (5 factorial) different ways to order columns in GraphQL query that produces 120 different cacheable queries with identical result that would in normal case be cached and reused but now is trashing your cache. This becomes more prominent in bigger team where everyone writes their own queries.

Thread Thread
kfwerf profile image
Kenneth van der Werf • Edited

thats very academic, but just don't do that then. i haven't seen an impact yet on our side, but what you are saying is probably true, sounds like the caching approach should be different, e.g. order on the fly. not saying its not a problem, i'm just saying were not having that problem, yet.

Or actually thinking about it, sounds like maybe caching in the wrong place, just cache the most used case and then sort on all the results? Otherwise i guess yeah you would need to cache for all those cases, taking up space.

Some comments have been hidden by the post's author - find out more