News for hackers. Stuff that matters.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by mxstbr on Thursday June 17, 2021 @05:33AM (#27537786)
Great questions Andy!

We do support wrapping payload types of any kind because we invalidate _all_ objects returned from a mutation. For example, if you run a mutation like editUser { user { id posts { id } } } we will invalidate any cached query result that contains that user and any cached query result that contains any of those posts!

You are right that smart invalidation can never be 100% reliable, which is why we have the Purging API to manually purge records you know changed from your backend. I think most customers are going to use the manual Purging API, however we also have a bunch of customers with use cases for whom the smart invalidation suffices.

Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by jorams on Thursday June 17, 2021 @06:25AM (#27538092)
I guess that means a mutation like `editUser { user { name } }` would not trigger smart invalidation, since there is no ID to work with?
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by mxstbr on Thursday June 17, 2021 @06:33AM (#27538135)
That's correct, however we also allow defining custom "Key fields", which is how you can tell us which fields are unique and should be invalidated by (e.g. "User.email").
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by nivertech on Thursday June 17, 2021 @06:47AM (#27538193)
Would UUIDs or Relay-style global IDs help to avoid manual purging here?
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by mxstbr on Thursday June 17, 2021 @07:44AM (#27538527)
Any kind of unique ID works, whether UUIDs, global IDs, incremented IDs, etc.