GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understan...
For further actions, you may consider blocking this person and/or reporting abuse
Nice.
When I first read about GraphQL, when FB made it open source, I remember they had a cache solution, that kept all the records, and it had a push-update cache mechanism, meaning when the servers mutated the data it updated the GraphQL cache too.
I presumed it was in all implementations, what happened to that?
Could it be dataloader?
github.com/graphql/dataloader
Short, concise, and perfect 👌👍
Thanks for sharing! Really helpful for interviewees.
Server side caching for GraphQL: How about caching it behind resolvers? Again it depends on us whether we need to club multiple resolver to cache it with one key or multiple. So, i don't think caching is an issue when it is related to server-side.
Yes, i agree that REST is more intuitive to handle. As this is what we have been handling pretty long time now. In case of GraphQL it has a different way.