caching questions about graphqlbundle HOT 2 CLOSED

thanks for answering. a data loader is very helpful but it depends on what kind of business logic.
the good part is that we wont need to handle cache invalidation, the negative part is scaling servers is more expensive than scaling reverse proxies,
maybe we'll have a varnish extension for graphql in the future, but still cache invalidation would be hard

from graphqlbundle.

Hi,
This is not so easy, because a query can be write different ways to request the same data. If your graphql server doesn't have many clients you can analyze queries and override controller to add http caching... The best is to cache app level, that what recommend Facebook right now. See dataloader-bundle or dataloader-php to give you a start on this ( combine with a persistent cache system it can do the work).

from graphqlbundle.