data-api-builder-caching
Configure Data API Builder result caching across L1 in-memory, L2 distributed (Redis), and HTTP Cache-Control behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Configure Data API Builder result caching across L1 in-memory, L2 distributed (Redis), and HTTP Cache-Control behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run SQL Commander as a companion container for browser-based SQL access, with optional Azure Container Apps configuration.
Orchestrate SQL Server and Data API Builder with .NET Aspire for local development, health-aware startup, and dashboard-driven diagnostics.
Add MCP Inspector to .NET Aspire AppHost for local SQL MCP Server validation and tool discovery.
Add SQL Commander to .NET Aspire for lightweight SQL browsing and query execution during local DAB development.
Use SQL Database Projects (.sqlproj) with .NET Aspire for declarative schema deployment via dacpac.
Deploy Data API Builder and SQL MCP Server to Azure App Service for Linux, with or without containers.
| name | data-api-builder-caching |
| description | Configure Data API Builder result caching across L1 in-memory, L2 distributed (Redis), and HTTP Cache-Control behavior. |
| license | MIT |
Cache-Control request headers.runtime.cache with a sane default ttl-seconds.cache: { enabled, ttl-seconds, level }; pick L1 (in-memory only) or L1L2 (default, adds distributed Redis when enabled).runtime.cache.level-2 with provider: redis, connection-string, and optional partition.Cache-Control: no-cache forces a database refresh and updates cache, while no-store prevents this response from populating or refreshing cache."runtime": {
"cache": {
"enabled": true,
"ttl-seconds": 30,
"level-2": { "enabled": true, "provider": "redis", "connection-string": "localhost:6379", "partition": "prod-api" }
}
},
"entities": {
"Book": { "cache": { "enabled": true, "ttl-seconds": 120, "level": "L1L2" } }
}
L2 isn't enabled globally, entities set to L1L2 silently behave as L1.Cache-Control response headers; it only reads request directives (no-cache, no-store).max-age and max-stale.data-api-builder-configdata-api-builder-restdata-api-builder-observability