4 ms·
Our GraphQL Edge Cache is based on Fastly's infrastructure, so we do use Varnish under the hood for the cache storage. In order to properly support GraphQL at t
by mxstbr 4y ago
Our GraphQL Edge Cache is based on Fastly's infrastructure, so we do use Varnish under the hood for the cache storage. In order to properly support GraphQL at the caching layer you have to understand GraphQL so you can do fine-grained invalidation.[0]
Essentially, our GraphQL Edge Cache is similar to a GraphQL client. It looks at the request body with the query & the response with the typenames and tags the cached query result with all the objects contained within. E.g. a getBlogPost query that fetches the blog post and its author will be tagged with BlogPost#asdf123 and User#gjkd489. Then we can invalidate whenever those specific objects change.
[0]: https://docs.stellate.co/docs/purging-api https://docs.stellate.co/docs/purging-api
- ushakov 4y agohow many businesses are having the problem you’re solving? is this number greater than 10? aren’t you scared Fastly and Cloudflare will just clone your moat once they see some demand for a service like yours?
- thevarunraja 4y agoAkamai already solved this https://developer.akamai.com/blog/2019/06/18/announcing-graphql-caching-capability-akamai-api-gateway https://developer.akamai.com/blog/2019/06/18/announcing-grap... But looks like they will build more out of the box integrations.
- timsuchanek 4y agoThe number is actually greater than 1,000 right now. No, we're not scared of Fastly or Cloudflare and are actually cooperating with them. What makes you think that "they will just clone the moat"?
- deleted 4y ago[deleted]
- andrewingram 4y agoThe question about how many people have the problem isn’t the same question as asking how many people you’ve managed to sign up, can you be clearer about what your number is referring to? I’ve signed up for many more services than I actually need/use, and even amongst ones I use, there are certainly some solving problems I don’t really have.