GraphCDN is now Stellate and raised $30M
stellate.co
GraphCDN is now Stellate and raised $30M
1–10 of 39 posts
Re: GraphCDN is now Stellate and raised $30M
#2(For a minute though I feared they pivoted into block chain and crypto though - somehow my mind made a connection for the new name there :shrug:)
Re: GraphCDN is now Stellate and raised $30M
#3Re: GraphCDN is now Stellate and raised $30M
#4The media keeps spinning the world is about to end and it is impossible to raise fund. And yet here we are. $30M
unless your product manager is trying to impersonate whatever FAANG he wants to work at
Re: GraphCDN is now Stellate and raised $30M
#5Definitely a good name change. "GraphCDN" locked the company in to basically one product (although an interesting one), while there are so many closely related ones it seems their customers have been telling them about as well. (For a minute though I feared they pivoted into block chain and crypto though - somehow my mind made a connection for the new name there :shrug:)
Re: GraphCDN is now Stellate and raised $30M
#6Definitely a good name change. "GraphCDN" locked the company in to basically one product (although an interesting one), while there are so many closely related ones it seems their customers have been telling them about as well. (For a minute though I feared they pivoted into block chain and crypto though - somehow my mind made a connection for the new name there :shrug:)
"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"
Re: GraphCDN is now Stellate and raised $30M
#7Definitely a good name change. "GraphCDN" locked the company in to basically one product (although an interesting one), while there are so many closely related ones it seems their customers have been telling them about as well. (For a minute though I feared they pivoted into block chain and crypto though - somehow my mind made a connection for the new name there :shrug:)
Good blockchain caching use cases though: https://stellate.co/blog/scaling-hasura-at-rmrk & 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, a…
blockchain use-case is just poor to say the least
Re: GraphCDN is now Stellate and raised $30M
#8Earlier quoted context omitted.
Good blockchain caching use cases though: https://stellate.co/blog/scaling-hasura-at-rmrk & 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, a…
GraphQL is just HTTP, why isn’t a caching proxy like varnish enough? blockchain use-case is just poor to say the least
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.
Re: GraphCDN is now Stellate and raised $30M
#9Earlier quoted context omitted.
GraphQL is just HTTP, why isn’t a caching proxy like varnish enough? blockchain use-case is just poor to say the least
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 qu…
aren’t you scared Fastly and Cloudflare will just clone your moat once they see some demand for a service like yours?