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:
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
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
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:
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