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

Feature request: kube group #226

Open
AnthonyHewins opened this issue Sep 13, 2023 · 0 comments
Open

Feature request: kube group #226

AnthonyHewins opened this issue Sep 13, 2023 · 0 comments

Comments

@AnthonyHewins
Copy link

AnthonyHewins commented Sep 13, 2023

I skimmed the README and I believe I understand what this package does, tell me if this is correct: I can mix and match various cache systems together and use it to chain things together, so I can tell the cache system "store this" and have it put it in redis, in memory, somewhere else, etc. Then I can say "get this" and it will check the in memory cache first, then if needed check redis, then if needed it will update all of the caches

Just two questions if that's all true:

  1. Is there a mechanism to invalidate caches across different systems, whether they be in kubernetes, containers, different IPs etc. It looks like it but just want to be sure
  2. Is it simple to include or exclude caches so when I'm developing locally I can configure it to use redis in a cluster, but not use it in a local environment when there's no cluster. Answer looks like yes but just making sure

So if all of that is true, I think to make this library useful for what I need is to have it implement kube group as a cache option, I can try to help with adding that but only if this is all true. Just need some guidance on contributing

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

1 participant