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

Is there a plan for supporting client caching? #1161

Open
vipcxj opened this issue Jul 16, 2020 · 5 comments
Open

Is there a plan for supporting client caching? #1161

vipcxj opened this issue Jul 16, 2020 · 5 comments

Comments

@vipcxj
Copy link

vipcxj commented Jul 16, 2020

The most important feature in redis 6 seems to be client caching. Is there a plan for supporting client caching?

@luin luin added the Redis 6.0 label Jul 25, 2020
@luin
Copy link
Collaborator

luin commented Jul 25, 2020

Thanks for bringing this up. It's not on the roadmap for the moment but I think it's nice to have. Any PRs and discussions are welcome.

@andrewdep
Copy link

We are wanting to use server assisted client side caching as well.

@metalcamp
Copy link

metalcamp commented Aug 9, 2021

Any updates on this topic? Interested to help, but not too familiar with libs internals.

Edit: sorry, didn't look through hard enough, found this issue which explains it all #1073

@eugene1g
Copy link

eugene1g commented Feb 9, 2022

Seems like supporting client-side caching is not likely for the near future #1504 (comment)

@marcbachmann
Copy link
Collaborator

Before the implementation of the resp3 protocol handler will be started, it would be useful to spec out an api and requirements for client side invalidation.

According to https://redis.io/topics/client-side-caching#two-connections-mode RESP2 would also already work with a PUB/SUB approach.

So anybody with a use-case or free time would be welcome to tackle that.

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

No branches or pull requests

6 participants