Support for Client-Side Caching (Tracking / Caching of Invalidation Messages)

[a-khakimov]

Hi!

Redis has supported client-side caching since version 6, allowing clients to locally cache read results and receive invalidation messages when keys change. This feature can significantly reduce latency and load for read-heavy applications.

Currently, redis4cats does not seem to support this feature (tracked or broadcast modes), nor does it expose a way to subscribe to invalidation messages.

It would be great to have:

• An API to enable client-side caching (CLIENT TRACKING with options)
• Support for processing invalidation messages (e.g., via Pub/Sub or RESP3 protocol handling)
• Integration with cache decorators or helpers for local caching

Are there any plans to support this in future versions? I'd be happy to contribute or help discuss the design if needed.

Thanks for your work!

[yisraelU]

Thank you for your interest in Redis4cats.
While there is no official roadmap for redis4cats, given that Lettuce supports client side caching, there most likely will be no issue adding it in.
In the next few weeks I'll take a look

[a-khakimov]

Yes, I’m aware that Lettuce supports client-side caching. Currently, to make use of this feature, I have to manually implement the CacheAccessor using the Java API, something like this:

val cacheAccessor: CacheAccessor[Array[Byte], Array[Byte]] = new CacheAccessor[Array[Byte], Array[Byte]] {

  override def get(key: Array[Byte]): Array[Byte] = ???

  override def put(key: Array[Byte], value: Array[Byte]): Unit = ???

  override def evict(key: Array[Byte]): Unit = ???
}

ClientSideCaching.enable(cacheAccessor, connection, TrackingArgs.Builder.enabled().noloop())

However, it would be great to have proper support on the Scala side — with a more idiomatic interface for working with client-side caching in the spirit of redis4cats. This would make integration much smoother and more natural for Scala developers.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.