Generated online config JSON can be cached until the data service reloads. Blocked by Response Caching Middleware's lack of support for cache eviction. - dotnet/aspnetcore#2622 - dotnet/aspnetcore#27387 An alternative is to implement our own in-memory cache. References: - [Response caching in ASP.NET Core | Microsoft Docs](https://docs.microsoft.com/en-us/aspnet/core/performance/caching/response) - [Cache in-memory in ASP.NET Core | Microsoft Docs](https://docs.microsoft.com/en-us/aspnet/core/performance/caching/memory) - [Response Caching Middleware in ASP.NET Core | Microsoft Docs](https://docs.microsoft.com/en-us/aspnet/core/performance/caching/middleware) - [A guide to caching in ASP.NET Core](https://www.devtrends.co.uk/blog/a-guide-to-caching-in-asp.net-core) - [Custom response caching in ASP.NET Core (with cache invalidation)](https://www.devtrends.co.uk/blog/custom-response-caching-in-asp.net-core-with-cache-invalidation)
Generated online config JSON can be cached until the data service reloads.
Blocked by Response Caching Middleware's lack of support for cache eviction.
An alternative is to implement our own in-memory cache.
References: