New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for surrogate keys #17

Open
ArnaudBrousseau opened this Issue Mar 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@ArnaudBrousseau
Copy link
Contributor

ArnaudBrousseau commented Mar 2, 2018

At the moment we have ID extraction support in URLs (through bulk endpoint support and enable_id_extraction) but surrogate keys would help to invalidate groups of resources across caches. See these docs on how Fastly uses them.

Another big difference with our current support is the fact that surrogate keys are driven by a header returned by the server. Keys can be arbitrary, representing experiment cohorts or deploy versions (things that aren't in the request or response object). For example:

200 OK
Surrogate-Key: elite musician myexperiment-enabled
Content-Type: text/json
{"name": "Bob", "last_name": "Dylan", "num_reviews": 42}

Surrogate key support enables invalidation of all "musician" or "elite" resources for instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment