Output-caching has multiple data storage options

[sebastienros]

Cache entries should be stored in configurable locations.
In-memory, filesystem, and hybrid stores (metadata in memory and content on disk) are planned.
Some stores are able to handle size limits.

The storage for cached entries can be extended by developers by implementing a service and registering it in DI.
Potential implementations: Redis, database, CosmosDB, table/blob storage, sqlite

[Manish082007]

As a developer, I desperately want the Output Caching storage options feature in Asp.Net Core 7.

[nixtar]

As a developer, I desperately want the Output Caching storage options feature in Asp.Net Core 7.

Agreed.
I was really looking forward to finally replacing iis+ARR plugin with yarp + output caching with disk backed storage across ~1500 remote sites.

Hopefully the storage is at least extendable in 7.
If so, perhaps an official nuget package for the "built in" storage options so they can be released and updated on a separate cycle to dotnet itself?

However, even with just memory storage this new output caching is very epic. Great job to everyone involved. 👍👍

[h3rmanj]

I'm hoping it will integrate nicely with the already existing IDistributedCache interface. This is the only thing stopping us from moving to the new .NET 7 Output Cache from a custom output cache implementation.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[adityamandaleeka]

We implemented a Redis output cache store in .NET 8: #48450

I'm going to leave this issue open but change the milestone since .NET 8 has shipped already.