Skip to content
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

JIT HTTP Caching #53

Open
coryodaniel opened this issue Dec 7, 2019 · 1 comment
Open

JIT HTTP Caching #53

coryodaniel opened this issue Dec 7, 2019 · 1 comment

Comments

@coryodaniel
Copy link
Owner

Cheaped out and skipped caching for the HTTP Provider. Importante

@coryodaniel coryodaniel added this to the 0.5 milestone Dec 7, 2019
@coryodaniel coryodaniel modified the milestones: 0.5.1, 0.6, 1.0, 1.1 Apr 20, 2020
@shanesveller
Copy link

shanesveller commented Jul 21, 2020

In Go SDKs and the kube Rust crate there are concepts called Informers and Reflectors. IIUC Informers are sort of a once-per-controller feed of changes to a certain resource type that various components react to through subscription. Reflectors are a sort of read-through hot cache that stores a local copy of the full list of a resource type, will answer queries from that, and can refresh on demand. In between deliberate refreshes it watches the same event stream that an Informer does (and much like Bonny uses).

In a similar vein to my comment on #10: I have some ideas around implementing these on top of the Watch abstraction, then emitting those events via Registry.dispatch to separate processes that do further fan-out in an Informer's case or do some internal cache book-keeping in a Reflector's case.

Grab bag of reference links:

@mruoss mruoss modified the milestones: 1.1, 1.2 Mar 13, 2022
@mruoss mruoss removed this from the 1.2 milestone Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants