I was wondering if there is a best-practice to implement something analog to outputcaching that still allows us to generate a small part of the response server-side, despite the rest being outputcached? We use the MVC razor pages to render responses server side.

There used to be a nuget called MvcDonutCaching that allowed us to do that in .NET framework 4.8 era but that’s deprecated.

Specifically, we need to integrate an ad platform into our solution but this ad platform is server-to-server, so cannot be embedded solely on the client-side. We obviously don’t want to give up the output caching we heavily use and rely on today to offload backend processing at peaks.