.NET API Review

[MarcGravell]

Further on the HybridCache / string thing (around 28:00); we could absolutely do a future thing where a TKey is used for L1, with a Func<TKey, string> for the IDistributedCache callback; one other constraint that we had to contend with on the choice of string was the *lack* of a generic L1 cache; if we had forced a TKey (which would presumably be commonly used with value-tuples for composite keys), then every L1 fetch would need boxing

[jodydonetti]

Super interesting review. And for a lot of the notes from the board (like the missing context param in the factory for evolvability) had a big “I know that feel” vibe, via the experience with FusionCache 😅

[MarcGravell]

On the HybridCache crossover: yes, we've discussed the possibility of making use of RCache as an alternative L1 backend; in particular, this allows some *future* (not current) HybridCache usage with typed keys (TKey) - which is something that is *not* currently available since the existing L1-esque abstractions offer object/string keys. However, HybridCache would *also* need API work to support that. I know of several consumers who could make use of HybridCache with a TKey key API