Our regular look at Salesforce Commerce Cloud focuses on an overview of Cache Partitions.

What is it?

The page cache partitioning feature enables you to selectively invalidate a portion of your page cache instead of invalidating the entire cache.

For example it is possible to edit products directly in Business Manager on a Production instance to make a quick fix but if the page that shows the product is cached, it might take a long time until the change appears in the storefront.

To make the change appear faster, you can invalidate the page cache for the entire site. This makes the change go into effect within fifteen minutes, but has a significant performance impact, because the entire page cache is regenerated for not only products, but PLP, home page, etc.

This is where cache partitions come in handy as you can create a partition for specific content types without impacting the performance of the whole site. Typical partitions that come with the latest Site Genesis code are PDP, Product Tiles (each search results and PLP), Content assets/slots and Home Page, to name just a few.

Why do I care?

Cache Partitions have two main advantages for you as a retailer:

  • If you have to clear the cache, you can clear only a partition of it, minimising disruption and keeping speed, and therefore conversion rate, high
  • Therefore, you have greater flexibility making ‘in-day’ changes instead of waiting for overnight replications

Cache partitions have a lot of uses - some examples are when you need to do a correction to content assets like a homepage banner, or correcting a product’s name.

What do I need to know?

Cache Partitions are available to all instances currently. For a guide on how to create a cache partition you can visit SCC documentation about this here.


Sign up to our weekly email Commerce Cloud Condensed to find out more!

Comment