orchardcore-caching
Scannednpx machina-cli add skill CrestApps/CrestApps.AgentSkills/orchardcore-caching --openclawOrchard Core Caching - Prompt Templates
Configure and Manage Caching
You are an Orchard Core expert. Generate code and configuration for caching strategies including response compression, dynamic cache, shape-level caching, cache invalidation, and distributed cache.
Guidelines
- Enable
OrchardCore.ResponseCompressionto compress HTTP responses with gzip or Brotli. - Enable
OrchardCore.DynamicCachefor shape-level output caching with dependency tracking. - Use
ISignalto invalidate cached entries when underlying data changes. - Use
IDistributedCachefor storing serialized data across multiple servers. - Use
IDynamicCacheServiceto programmatically manage dynamic cache entries. - Use
CacheContextto declare cache dependencies, vary-by keys, and expiration policies. - Cache tag helpers in Razor and
{% cache %}blocks in Liquid provide declarative shape caching. - All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier.
Enabling Caching Features
{
"steps": [
{
"name": "Feature",
"enable": [
"OrchardCore.ResponseCompression",
"OrchardCore.DynamicCache"
],
"disable": []
}
]
}
Response Compression
Enable OrchardCore.ResponseCompression to add gzip and Brotli compression to HTTP responses. This module registers ResponseCompressionMiddleware and does not require additional code. Configure compression providers in Startup if custom settings are needed:
public sealed class Startup : StartupBase
{
public override void ConfigureServices(IServiceCollection services)
{
services.Configure<BrotliCompressionProviderOptions>(options =>
{
options.Level = System.IO.Compression.CompressionLevel.Fastest;
});
services.Configure<GzipCompressionProviderOptions>(options =>
{
options.Level = System.IO.Compression.CompressionLevel.SmallestSize;
});
}
}
Dynamic Cache (Shape-Level Caching)
OrchardCore.DynamicCache caches the rendered HTML output of shapes. Each cached shape tracks dependencies so it can be evicted when related content changes. Dependencies use the format contentitemid:{id} or custom signal names.
Shape Cache Tag Helper (Razor)
Use the <cache> tag helper in Razor views to cache rendered shape output with vary-by attributes:
<cache expires-after="TimeSpan.FromMinutes(10)"
vary-by-route="area,controller,action"
vary-by-query="page">
@await DisplayAsync(Model.Content)
</cache>
Supported vary-by attributes:
vary-by-route- Vary by route values.vary-by-query- Vary by query string parameters.vary-by-user- Vary by authenticated user.vary-by-cookie- Vary by cookie values.vary-by-header- Vary by request headers.vary-by- Vary by a custom string key.expires-after- Absolute expiration asTimeSpan.expires-sliding- Sliding expiration asTimeSpan.expires-on- Absolute expiration asDateTimeOffset.
Liquid Cache Block
In Liquid templates, use the {% cache %} tag for shape-level caching:
{% cache "my-cache-key", after: "00:10:00", vary_by: Request.QueryString["page"] %}
{{ Model.Content | shape_render }}
{% endcache %}
Using CacheContext for Shape Dependencies
Shapes can declare caching behavior through CacheContext. In a shape display driver, configure cache parameters:
using OrchardCore.DisplayManagement.Handlers;
using OrchardCore.DisplayManagement.Views;
using OrchardCore.Environment.Cache;
public sealed class RecentPostsDisplayDriver : DisplayDriver<RecentPostsViewModel>
{
public override IDisplayResult Display(RecentPostsViewModel model, BuildDisplayContext context)
{
return View("RecentPosts", model)
.Location("Detail", "Content:5")
.Cache("recentposts", cache => cache
.AddDependency("contenttype:BlogPost")
.AddContext("user")
.WithExpiryAfter(TimeSpan.FromMinutes(15))
);
}
}
Common CacheContext methods:
AddDependency(string)- Evict when the named dependency signals.AddContext(string)- Vary by the named context (e.g.,"user","route").WithExpiryAfter(TimeSpan)- Set absolute expiration.WithExpirySliding(TimeSpan)- Set sliding expiration.
Cache Invalidation with ISignal
ISignal triggers cache eviction by signaling a named dependency. Any dynamic cache entry tracking that dependency is purged:
using OrchardCore.Environment.Cache;
public sealed class ProductService
{
private readonly ISignal _signal;
public ProductService(ISignal signal)
{
_signal = signal;
}
public async Task InvalidateProductCacheAsync()
{
await _signal.SignalTokenAsync("productcatalog");
}
}
Shapes or code that depend on "productcatalog" are evicted when the signal fires. Content item changes automatically signal contentitemid:{ContentItemId} dependencies.
Using IDistributedCache
IDistributedCache stores serialized data in a shared cache backend (memory, SQL Server, or Redis). Inject and use it directly:
using Microsoft.Extensions.Caching.Distributed;
public sealed class CatalogCacheService
{
private readonly IDistributedCache _distributedCache;
public CatalogCacheService(IDistributedCache distributedCache)
{
_distributedCache = distributedCache;
}
public async Task<string?> GetCachedCatalogAsync(string key)
{
return await _distributedCache.GetStringAsync(key);
}
public async Task SetCachedCatalogAsync(string key, string value)
{
var options = new DistributedCacheEntryOptions
{
AbsoluteExpirationRelativeToNow = TimeSpan.FromMinutes(30),
SlidingExpiration = TimeSpan.FromMinutes(10),
};
await _distributedCache.SetStringAsync(key, value, options);
}
public async Task RemoveCachedCatalogAsync(string key)
{
await _distributedCache.RemoveAsync(key);
}
}
Using IDynamicCacheService
IDynamicCacheService provides programmatic access to the dynamic cache for storing and evicting pre-rendered HTML:
using OrchardCore.DynamicCache;
public sealed class WidgetCacheManager
{
private readonly IDynamicCacheService _dynamicCacheService;
private readonly ISignal _signal;
public WidgetCacheManager(
IDynamicCacheService dynamicCacheService,
ISignal signal)
{
_dynamicCacheService = dynamicCacheService;
_signal = signal;
}
public async Task<string?> GetCachedWidgetAsync(CacheContext context)
{
return await _dynamicCacheService.GetCachedValueAsync(context);
}
public async Task SetCachedWidgetAsync(CacheContext context, string htmlContent)
{
await _dynamicCacheService.SetCachedValueAsync(context, htmlContent);
}
public async Task InvalidateWidgetAsync()
{
await _signal.SignalTokenAsync("widget-sidebar");
}
}
Redis Distributed Cache Configuration
To use Redis as the distributed cache backend, add the Microsoft.Extensions.Caching.StackExchangeRedis package to the web project and configure it:
public sealed class Startup : StartupBase
{
private readonly IConfiguration _configuration;
public Startup(IConfiguration configuration)
{
_configuration = configuration;
}
public override void ConfigureServices(IServiceCollection services)
{
services.AddStackExchangeRedisCache(options =>
{
options.Configuration = _configuration["Redis:ConnectionString"];
options.InstanceName = "orchardcore-";
});
}
}
Corresponding appsettings.json:
{
"Redis": {
"ConnectionString": "localhost:6379,abortConnect=false,connectTimeout=5000"
}
}
Cache Profiles and Cache-Control Headers
Configure response cache profiles to set Cache-Control headers for HTTP responses:
public sealed class Startup : StartupBase
{
public override void ConfigureServices(IServiceCollection services)
{
services.AddResponseCaching();
services.AddMvc(options =>
{
options.CacheProfiles.Add("Default", new CacheProfile
{
Duration = 300,
Location = ResponseCacheLocation.Any,
VaryByHeader = "Accept-Encoding",
});
options.CacheProfiles.Add("NoCache", new CacheProfile
{
Duration = 0,
Location = ResponseCacheLocation.None,
NoStore = true,
});
});
}
}
Apply a cache profile to a controller or action:
[ResponseCache(CacheProfileName = "Default")]
public sealed class CatalogController : Controller
{
public IActionResult Index()
{
return View();
}
[ResponseCache(CacheProfileName = "NoCache")]
public IActionResult Checkout()
{
return View();
}
}
Caching Content Queries
Combine IDistributedCache with content queries to avoid repeated database calls:
using System.Text.Json;
using Microsoft.Extensions.Caching.Distributed;
using OrchardCore.ContentManagement;
using OrchardCore.Environment.Cache;
public sealed class CachedArticleService
{
private readonly IContentManager _contentManager;
private readonly IDistributedCache _distributedCache;
private readonly ISignal _signal;
public CachedArticleService(
IContentManager contentManager,
IDistributedCache distributedCache,
ISignal signal)
{
_contentManager = contentManager;
_distributedCache = distributedCache;
_signal = signal;
}
public async Task<IEnumerable<ContentItem>> GetPublishedArticlesAsync()
{
var cacheKey = "published-articles";
var cached = await _distributedCache.GetStringAsync(cacheKey);
if (cached is not null)
{
return JsonSerializer.Deserialize<IEnumerable<ContentItem>>(cached)
?? [];
}
var articles = await _contentManager
.GetAsync(VersionOptions.Published);
var options = new DistributedCacheEntryOptions
{
AbsoluteExpirationRelativeToNow = TimeSpan.FromMinutes(10),
};
await _distributedCache.SetStringAsync(
cacheKey,
JsonSerializer.Serialize(articles),
options);
return articles;
}
public async Task InvalidateArticleCacheAsync()
{
await _distributedCache.RemoveAsync("published-articles");
await _signal.SignalTokenAsync("contenttype:Article");
}
}
Source
git clone https://github.com/CrestApps/CrestApps.AgentSkills/blob/main/src/CrestApps.AgentSkills/orchardcore/orchardcore-caching/SKILL.mdView on GitHub Overview
This skill covers configuring and managing caching in Orchard Core, including response compression, dynamic shape caching, cache tag helpers, ISignal-based invalidation, and distributed cache with Redis. It emphasizes using CacheContext dependencies and IDynamicCacheService to ensure fast, scalable performance with fresh content.
How This Skill Works
Enable the relevant caching modules (e.g., OrchardCore.ResponseCompression and OrchardCore.DynamicCache), wire in IDistributedCache for cross-server storage, and use IDynamicCacheService to manage dynamic cache entries. Shapes can declare dependencies via CacheContext, while declarative caching is added through Razor cache tag helpers and Liquid cache blocks to control vary-by keys and expirations.
When to Use It
- You need HTTP response compression to reduce bandwidth and improve perceived performance.
- You want shape-level output caching with dependency tracking for dynamic content updates.
- You require cache invalidation when underlying data changes using ISignal-based signals.
- Your deployment spans multiple servers and benefits from a Redis-backed distributed cache.
- You want declarative, template-driven caching in Razor or Liquid with explicit vary-by and expiration rules.
Quick Start
- Step 1: Enable features: { "steps": [ { "name": "Feature", "enable": ["OrchardCore.ResponseCompression", "OrchardCore.DynamicCache"], "disable": [] } ] }
- Step 2: Implement dynamic cache logic using IDynamicCacheService and declare dependencies with CacheContext for your shapes.
- Step 3: Add cache blocks in Razor or Liquid templates (e.g., <cache ...> in Razor or {% cache ... %} in Liquid) and test eviction on data changes.
Best Practices
- Enable OrchardCore.ResponseCompression and OrchardCore.DynamicCache in your feature recipes before heavy caching.
- Prefer ISignal-based invalidation to evict caches when related content or data changes.
- Use IDynamicCacheService to programmatically create, update, and clear dynamic cache entries.
- Declare dependencies, vary-by keys, and expiration policies using CacheContext for predictable eviction.
- Leverage cache tag helpers in Razor and Liquid {% cache %} blocks to apply consistent caching rules across templates.
Example Use Cases
- Enable gzip/Brotli by turning on ResponseCompression and use DynamicCache for shape-level caching on frequently rendered pages.
- Cache a product listing with a Redis-backed IDistributedCache and invalidate when product data updates via ISignal.
- Use a Razor <cache> tag with vary-by-route and expires-after to cache a layout component.
- Use Liquid {% cache %} with a content item dependency to cache a content-rich block across requests.
- Configure a CacheContext in a shape display driver to declare dependencies, vary-by keys, and sliding expiration.