Ask HN: Is (Web) Cacheing Broken?
5 by ggm | 1 comments on Hacker News.
There's your own markup and how it asserts cache lifetime (or not) There's the subtle changes made on-the-fly by smart boxes in between you and the outside world. There's cacheing in the GCP buckets, Amazon S3 buckets. There's cacheing in your frontend CDN. There's DNS cacheing. There's in-browser cacheing, differentially for page content, for crypto assets like X509 certificates, for DNS FQDN query results. Maybe it's just me, but it "feels" like we have a cache problem at scale: * you can't update your own cache lifetime without strong likelihood somebody else erodes it. * you can't easily flush all these caches. Some of them are at scale held by millions of things. * they interact!