Does this library support the resp3 client side caching model?

[tim1003simon]

Wondering if support for https://redis.io/docs/latest/develop/reference/client-side-caching/ has been added to this library..?

[mgravell]

Great question. Support for client-side-caching is definitely in the plan for attention on the "sooner" side - it isn't quite at the top of the list yet, though - I'm working through active-active (geo-redundancy) first; but definitely a highly wanted feature. It is likely (but not certain) that the development for this will actually happen over in SE.Redis, since some of the nuances are likely to require direct library support, but that is perhaps a moot distinction since I'm equally involved in both!

[mgravell]

For today, options include:

• HybridCache (and FusionCache) offer an abstraction of the over-arching cache APIs
  • IIRC, FusionCache has cooperative invalidation (meaning: I believe the library causes the invalidation, presumably via pub/sub, but don't quote me on that; @jodydonetti would know more)
  • HybridCache does not have active invalidation, purely passive via time expiration
• more manual options with your own cache:
  • now that SE.Redis has full support for keyspace/keyevent notifications it should be possible to hook things up to server-generated events (/cc @jodydonetti for interest)
  • you can use your own manual pub/sub

Timing wise: I would hope to have a library-inbuilt client-side-caching implementation within a few months, but this is not a hard commitment by me.

Minor note: RESP3 is not a pre-requisite for CSC - there is a REDIRECT option for RESP2 clients, but: I would expect any implementation of CSC works appropriately for both RESP2 and RESP3 usage. My personal preference is also to implement CSC with support a variety of invalidation modes via the same API (other than configuration, obvs):

• using the CSC server feature, with support for both key-tracking and broadcast mode (with prefix)
• using keyspace/keyevent notifications
• using library-generated pub/sub on a user-supplied invalidation channel