FastQL

Now part of @GraphCDN

[FastQL @FastQL]

FastQL is joining @GraphCDN! 🎉⚡️

60 edge locations, analytics, advanced cache controls, and amazing team @mxstbr @TimSuchanek

[Stellate ⚡️ @Stellate]

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: https://t.co/rlfCpDPnEi ⚡️

[FastQL @FastQL]

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
https://t.co/DVZYWS0GkF

[FastQL @FastQL]

@zdne @GraphQL We think cacheable should be a ✔️ for GraphQL :)

[FastQL @FastQL]

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.
https://t.co/81oxYBlfz2

[Steven Mercatante @mercatante]

I think the #GraphQL ecosystem can be confusing, especially to newcomers, so I built a chart that shows how all the pieces interconnect.

https://t.co/nAWwNxIARv

Includes tools from the major players, like @apollographql, @graphcool, @FormidableLabs, & others. PRs welcome!

[FastQL @FastQL]

"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 https://t.co/8BO55eGFuz

[John Resig @jeresig]

I'm excited to announce the beta release of The GraphQL Guide, a new book about GraphQL I'm co-authoring with @lorendsr! https://t.co/S1YfL72vfz

[FastQL @FastQL]

Really fantastic academic take on how to analyze complexity of GraphQL queries and their responses via @adriancolyer @olafhartig @perez
https://t.co/rt7DLf0O9z

[FastQL @FastQL]

@notrab Thanks Jamie!!

[FastQL @FastQL]

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 https://t.co/mOndLS6FW8

[FastQL @FastQL]

"Every REST API is a snowflake" pretty much sums up why our service is GraphQL only
https://t.co/xflv2u91Bc

[FastQL @FastQL]

@erinfoox @GraphQL I haven't seen APIs that expose page metadata results. I've seen a pattern of fetching the next page of results, and if it's empty w/ no error, then you can assume you're at the end.

Could be interesting to have a "Paginator" interface that exposes page info though.

[FastQL @FastQL]

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. https://t.co/oo7l3s6CYK

[Phil Sturgeon @philsturgeon]

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. https://t.co/Z73vjt6ivr

[FastQL @FastQL]

@philsturgeon @pmerikan 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.

[FastQL @FastQL]

@adrianpike Not going to lie, in my first prototype I found an off-by-one error in a poorly named cache invalidation method

[FastQL @FastQL]

@imkmf Agreed! Funny enough we just went live on PH this morning: https://t.co/IrwQcOPebp

[FastQL @FastQL]

@danbucholtz Not blasphemy, always do what works best! Curious what you're running into with mutations?

[FastQL @FastQL]

The beta is finished! We have a new look, and anyone can sign up now! Sign up, enter your GraphQL endpoint, and you're ready to go. Couldn't be easier...