FastQL is joining @GraphCDN! 🎉⚡️
60 edge locations, analytics, advanced cache controls, and amazing team @mxstbr @TimSuchanek
FastQL retweeted
We're thrilled to announce that we have acquired @FastQL, the first GraphQL CDN! 🎉
We're delighted to have @zhobbs in our corner advising us and will be transitioning all FastQL customers to GraphCDN over the coming months: graphcdn.io/blog/graphcdn-ac… ⚡️
Check out @PulumiCorp's launch announcement today. Anyone else looking forward to spec'ing all their infrastructure in JS/TS/Golang instead of Yaml? #DevOps
joeduffyblog.com/2018/06/18/…
Great guide by @mdlavin on using AWS X-Ray to find and resolve your #GraphQL performance problems. Also, X-Ray works with many different languages, not just node.
medium.com/lifeomic/introduc…
FastQL retweeted
I think the #GraphQL ecosystem can be confusing, especially to newcomers, so I built a chart that shows how all the pieces interconnect.
graphqlstack.com/
Includes tools from the major players, like @apollographql, @graphcool, @FormidableLabs, & others. PRs welcome!
"I’ve been doing a lot of thinking about what a new generation of web APIs would look like, and I for one, would like to see more #GraphQL" - @brandur of @stripe brandur.org/graphql
FastQL retweeted
I'm excited to announce the beta release of The GraphQL Guide, a new book about GraphQL I'm co-authoring with @lorendsr! blog.graphql.guide/introduci…
Really fantastic academic take on how to analyze complexity of GraphQL queries and their responses via @adriancolyer @olafhartig @perez
blog.acolyer.org/2018/05/21/…
CRUD boilerplate can be pretty tedious, with REST or with #GraphQL. Excited to see the work going on with the 'graphql-boilerplates' project. Hope to see #Python, #Elixir, and #Golang on there one day github.com/graphql-boilerpla…
"Every REST API is a snowflake" pretty much sums up why our service is GraphQL only
xitter.cf/joshPandaEdward/status…
Thanks @philsturgeon ! We agree that read-heavy use cases work great for FastQL, the higher the hit rate the more benefit you'll get from edge caching. xitter.cf/philsturgeon/status/10…
I'm recommending my GraphQL colleagues check out @FastQL, but it's only going to cover a few use-cases. For read-heavy APIs this is seems ideal, but write-heavy systems maybe need something else. xitter.cf/philsturgeon/status/10…
Good point, and agree that for some things TTL does make sense. Cache-control headers are respected, and sending invalidations to us is optional, so we give flexibility there.
Not going to lie, in my first prototype I found an off-by-one error in a poorly named cache invalidation method
Agreed! Funny enough we just went live on PH this morning: producthunt.com/posts/fastql
