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

Using caching and TRACKING invalidation process #2504

Closed
MosheLOptimove opened this issue May 11, 2023 · 2 comments
Closed

Using caching and TRACKING invalidation process #2504

MosheLOptimove opened this issue May 11, 2023 · 2 comments

Comments

@MosheLOptimove
Copy link

Hello,

We are working on a real-time application (i.e. low latency requirement) and have a REDIS data source. Currently we have an internal caching package that overrides node-redis' functionalities.

I'm trying to see if we can deprecated that package and use the formal package instead, but I couldn't find any example for using caching (or the new TRACKING functionality). Does a caching mechanism exists in this package? and if so, can you point me to some code-based resources?

Thanks,
Moshe

@leibale
Copy link
Contributor

leibale commented May 11, 2023

I'm assuming you are talking about "client-side caching"? The plan is:
5.0: RESP3 + more features
5.1: Sentinel support
5.2: Client-side caching

Duplicate of #1623

@leibale leibale closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2023
@MosheLOptimove
Copy link
Author

Thanks, I'll subscribe to that issue

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

2 participants