I've been working on an open source implementation of a Stellate (https://stellate.co) like GraphQL cache service, and it's finally hit v0.1 TL,DR; It is a cached proxy for your GraphQL API with automatic purging. Deploy it in front of GraphQL API, and it will start caching all requests passing through it. - Source: Hacker News / 7 months ago

Stellate - Stellate is a blazing-fast, reliable CDN for your GraphQL API and free for two services. - Source: dev.to / about 1 year ago

While some of the metrics aren't particularly helpful (depending on the actual company being evaluated) as others have mentioned, the round sizes are in the right ballpark. Our[0] actual round sizes were: 1. Pre-seed: $1M (led by System.One) 2. Seed: $4M (led by Boldstart) 3. Series A: $25M (led by Tiger Global) Note that all of these were all raised in 2021 & 2022 before the investment market crash, but even now... - Source: Hacker News / almost 2 years ago

For server-side caching, you have neat solutions like GraphCDN or plugins (eg. The envelop plugin with GraphQL Yoga). - Source: dev.to / almost 3 years ago

Out of the thousands of production GraphQL APIs we've seen at GraphCDN, the two most common pre-made GraphQL APIs are Hasura and WPGraphQL! Source: about 3 years ago

'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 2 years ago

> Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / almost 3 years ago

> Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / almost 3 years ago

This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / almost 4 years ago