News for hackers. Stuff that matters.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by coffeedoughnuts on Thursday June 17, 2021 @05:22AM (#27537693)
> Using a normal restful HTTP api has none of these issues

I don't think a normal HTTP api provides anything to help with cache invalidation after a write operation, does it?

Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by simplyinfinity on Thursday June 17, 2021 @08:10AM (#27538717)
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ET...

Etags can be used to check and invalidate content.

Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by timsuchanek on Thursday June 17, 2021 @09:04AM (#27539142)
Yes, but as long as a cached version is still returned at the edge (while the real content might have changed), the ETag won't help. It can only save you from unnecessarily downloading content you already have - in case it didn't change.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by simplyinfinity on Thursday June 17, 2021 @09:43AM (#27539463)
And when the content is updated you return different etag and the content is refreshed. Your system should have either distributed cache or a way for the edge to detect cache invalidations or for you to manually invalidate the cache on the edge.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by timsuchanek on Thursday June 17, 2021 @11:01AM (#27540299)
Exactly, that is what we provide. Including Etag support btw.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by doteka on Thursday June 17, 2021 @09:00AM (#27539112)
As other commenters have mentioned, in fact it has functionality specific for this purpose. That is part of the underlying reason for my question: it often feels like the people pushing for graphql adoption are not aware what http is capable of out of the box.
Re:Show HN: GraphCDN – GraphQL CDN with edge caching and ana... by timsuchanek on Thursday June 17, 2021 @05:25AM (#27537728)
+1