When Fastly sends request to a backend it can respond w/ ‘Surrogate-Keys’ header to set up caching associations. Is it possible to remove those associations with the same response?
E.g. backend provides ‘Purged-Surrogate-Keys’ while responding with the list of keys to purge (e.g. keys which were affected during the request) so there is no need to hit Fastly API in background w/ every single key from this list. This should both increase cache invalidation speed and reduce traffic between Fastly and a backend.
Another option can be bulk purge API which accepts multiple surrogate keys at once.
Please sign in to leave a comment.