Here is an issues with detailed description: NekR/offline-plugin#77

In some cases, the default implementations are very inefficient (e.g. Map.replaceAll and forEach fetching all entries and iterating over them locally). This was improved on member-side as the cluster version is available and in some cases we opted for using entry processors instead.

On the client-side, the cluster version is not available which meant it ends up still using the default versi

currently "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Problem description

I saw comment about nulls caching dotnetcore/EasyCaching#43 (comment), but we have important case when it is necessary.

We develop a low code platform, where our clients can set up some handlers for processing some requests from there websites.

1. Each handler is entity in database, that is cached in memory.
2. Some handlers cou