Cache
Cache management in DynamicWeb 10
The Cache tool in DynamicWeb 10 provides developers and technical partners with detailed insights into the platform’s caching layers. DynamicWeb uses cache internally in different ways to maintain system performance.
The cache UI will give an insight to what the cache contains and makes it possible to reset some parts of it if needed.
Types of cache
DynamicWeb utilizes multiple caching layers, with service cache to be most important, to store different types of runtime data. You can view and interact with the following cache types:
Static types
Stores precompiled or statically defined data structures such as .NET type metadata. These caches are rarely cleared unless major application-level changes occur.
Memory caches
These are fast, in-memory runtime caches that store frequently accessed objects like content templates, navigation structures, or settings.
Session caches
Session-specific data used for temporary storage—such as user preferences or shopping cart state. Automatically cleared when a user session expires or is restarted.
Service caches
Back-end data retrieved from database and stored in the service cache for fast lookups. These caches can be cleared manually in certain scenarios (see below).
Managing service caches
Service caches can be selectively cleared using the context menu available in the list view. This action forces a cache refresh for that particular service, which is useful when the underlying data source has been updated but the changes are not yet reflected in the frontend or application logic.
Usually the service caches will be cleared if needed by DynamicWeb. But when data is added in integrations or directly in the database or some other way than using the designated APIs, the cache can contain stale data and be refreshed manually.
Note
Clearing a service cache in a production environment can increase server load temporarily, as the data will need to be fetched again from the external source.
Common scenarios
| Scenario | Recommended Cache Action |
|---|---|
| Product details updated in ERP but not visible on the website | Clear the Product-related service caches |
Best practices
- Avoid indiscriminate cache clearing in production environments.
- Monitor memory usage if frequent memory cache purges are necessary.
- Coordinate service cache refreshes in integration jobs.