b2c-custom-caches

To cache expensive API responses in B2C Commerce, define a cache ID in your cartridge's caches.json and use CacheMgr.getCache to store and retrieve the response data across requests.

CacheMgr works by retrieving application-local caches scoped per application server. You use the getCache method to access a cache instance, then put and get methods to store and retrieve expensive data with optional expiration.

Yes, you need caches.json to declare cache IDs and expiration settings within your cartridge before you can retrieve and use those caches via CacheMgr.getCache in your B2C Commerce code.

The best way to cache site configuration data in B2C Commerce is defining a custom cache in caches.json and accessing it with CacheMgr to reduce repeated expensive calculations and external calls.

Yes, you can set optional expiration times for custom caches in B2C Commerce by defining the expiration parameters within your cartridge's caches.json file when declaring the cache ID.

Custom cache values do not persist across application servers because B2C Commerce caches are scoped per application server, meaning data stored locally on one server is not shared with another.