SV 1 sites can leverage http caching layers such as Varnish / Fastly, because most of the requests are method:GET.
By default, Apollo asumes method:POST requests. We might be able to just switch to GET within Apollo and tune the Varnish configs at the graphql endpoint, but we might be working against some querystring lenght limitations on Fastly.
It might also be possible to cache POST requests just at that GraphQL endpoint, but we may even prefer an explicit cacheable endpoint / disallow caching of requests that use mutations or actually vary on a user cookie.
SV 1 sites can leverage http caching layers such as Varnish / Fastly, because most of the requests are
method:GET
.By default, Apollo asumes
method:POST
requests. We might be able to just switch toGET
within Apollo and tune the Varnish configs at the graphql endpoint, but we might be working against some querystring lenght limitations on Fastly.It might also be possible to cache POST requests just at that GraphQL endpoint, but we may even prefer an explicit cacheable endpoint / disallow caching of requests that use mutations or actually vary on a user cookie.
Possibly related to upgrading Apollo (https://github.com/scaife-viewer/frontend/issues/12)