sfcc-caching

Manage SFCC storefront caches with caches.json and CacheMgr.

27|9|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-caching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfcc-caching
Source: https://github.com/taurgis/sfcc-dev-mcp/tree/main/ai-instructions/skills/sfcc-caching
Command: npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-caching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Caching in SFCC can dramatically reduce latency and backend load by selecting the right cache layers (page cache, custom cache via CacheMgr, and service response cache) and applying correct invalidation and TTL strategies.

Core Features & Use Cases

  • Choose the appropriate cache layer (page cache, custom cache (CacheMgr), service response cache) to optimize performance and resource usage.
  • Design keys with site and locale scoping, use atomic get-or-load patterns, and cache POJOs rather than heavy API objects.
  • Monitor hit ratios and write failures using Business Manager, adjusting TTLs to balance freshness and responsiveness.
  • Ensure proper registration of caches in caches.json via cartridge package.json, and maintain immutable cached values to prevent in-place mutations.

Quick Start

Configure a cartridge-level caching strategy using caches.json and CacheMgr to minimize repeated data lookups.

Frequently Asked Questions about sfcc-caching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement custom cache management in SFCC to reduce storefront latency?

SFCC cache management reduces latency by applying correct TTLs and invalidation strategies across page, custom CacheMgr, and service response caches. You configure caches.json via cartridge package.json and use atomic get-or-load patterns.

What's the best way to register custom caches in SFCC using caches.json?

Registering custom caches in SFCC requires defining them in caches.json through your cartridge package.json. This ensures proper CacheMgr usage, consistent cache keys scoped by site and locale, and maintained immutable cached values to prevent in-place mutations.

When should I use page cache versus custom CacheMgr in SFCC?

Use page cache for full storefront pages, custom CacheMgr for specific data objects, and service response cache for external API calls. Selecting the appropriate SFCC cache layer optimizes performance and resource usage while balancing freshness and responsiveness.

How do I monitor SFCC cache hit ratios and write failures in Business Manager?

Monitor SFCC cache hit ratios and write failures using Business Manager tools. Analyzing these metrics allows you to adjust TTLs and invalidation strategies, ensuring a balance between data freshness and storefront responsiveness across multi-node deployments.

Why should I cache POJOs instead of heavy API objects in SFCC CacheMgr?

Caching POJOs in SFCC CacheMgr prevents memory bloat and serialization issues. Heavy API objects risk in-place mutations, whereas immutable cached POJOs ensure consistent state across multi-node deployments and maintain cache data integrity.

Does SFCC caching support atomic get-or-load patterns for multi-node deployments?

SFCC caching supports atomic get-or-load patterns for multi-node deployments requiring consistent cache keys and TTLs. This pattern minimizes repeated data lookups and ensures synchronized cache behavior across all storefront nodes.