4 ms·

Good blockchain caching use cases though: https://stellate.co/blog/scaling-hasura-at-rmrk https://stellate.co/blog/scaling-hasura-at-rmrk & https://stellate.co/

by drodio 4y ago

Good blockchain caching use cases though: https://stellate.co/blog/scaling-hasura-at-rmrk https://stellate.co/blog/scaling-hasura-at-rmrk & https://stellate.co/blog/super-fast-hasura-graphql-for-stxnft https://stellate.co/blog/super-fast-hasura-graphql-for-stxnf... "Given that the Bitcoin blockchain only produces new blocks once about every 10 minutes, Gamma’s data also changes at most every 10 minutes — making it an ideal use case for caching. Thomas added Gamma’s GraphQL edge cache in front of Gamma’s Hasura GraphQL API, and immediately got an overall cache hit rate of 87%, which corresponds directly to a decrease in traffic to their Hasura instance. Even better, their two most highly requested queries are sitting at a 97% and 92% cache hit rate, respectively"

ushakov 4y ago
GraphQL is just HTTP, why isn’t a caching proxy like varnish enough? blockchain use-case is just poor to say the least
- 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 ago
    how 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 ago
      Akamai 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 ago
      The 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 ago
        The 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.

by drodio 4y ago

ushakov 4y ago

GraphQL is just HTTP, why isn’t a caching proxy like varnish enough? blockchain use-case is just poor to say the least

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 ago
  how 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 ago
    Akamai 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 ago
    The 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 ago
      The 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.