Question : How are cache invalidations handled? about fusioncache HOT 10 CLOSED

from fusioncache.

Hi @MartyBJones , thanks for considering FusionCache.

The scenario you are talking about is an example of why I'm working on adding a backplane (see #11), which I hope will be available soon.
Btw you caught me working on it right at this very moment 😅

Another approach which would give similar results is to have a very low memory cache duration along with a higher distributed cache duration (like requested in #30) to highly reduce the differences between the memory and the distributed cache.

from fusioncache.

from fusioncache.

Hi @MartyBJones , I'm happy to say that I've finally been able to complete the design and implementation of the backplane feature.

Please take a look here, try it out and let me know what you think so I can move forward with the final version.

Thanks 🙏

📦 It's a pre-release!

Note that the Nuget package is marked as pre-release so please be sure to enable the related filter otherwise you would not see them:

from fusioncache.

Meanwhile I published an (hopefully) even better alpha2 release.

from fusioncache.

Hi all, just wanted to update you on the next version: I released right now the BETA2 for the next big release, which includes among other small things a big fix for the DI setup part.

This will probably be the last release before the official one.

from fusioncache.

Hi all, yesterday I released the BETA 3.

Unless some big problem comes up, this will be the very last release before the official one, which will be in the next few days 🎉

from fusioncache.

Closing this since with v0.9.0 the backplane is an official feature, with official docs and more.

from fusioncache.

from fusioncache.

Hi @MartyBJones , there are no intrinsic limits on how many notifications it can handle, it wholly depends on the underlying pub/sub mechanism used.

For example using the common Redis implementation on, say, an Azure Redis Cache instance will be subjected to the limits of that infrastructure and the Redis internal limits themselves (some of which you can see here).

In general I haven't found any particular bottlenecks or problems in general regarding the pub/sub part (which is what is used in the backplane), but I don't have precise number yet.

from fusioncache.