Data Expiration Strategies in Cache

NCache supports time-based data invalidation, allowing cache items to expire after a specified duration or interval. This is useful when the expected frequency of data changes is known. For example, region metadata that updates infrequently can safely expire on a schedule. By utilizing Absolute Expiration with a known validity period and Sliding Expiration for session-based or idle data, NCache automatically removes stale entries and helps maintain application performance and data freshness.

Time-based expiration also helps reduce the possibility of clients receiving stale data. For instance, if product inventory is updated in the database but not yet reflected in the cache, expiring the stale cache entry allows the application to load the latest data on the next request. It is equally effective for session management: sessions that remain idle for a defined period can be automatically removed from the cache.

In This Section

Data Expiration Overview
Explains use cases and behaviors for Absolute Expiration, Sliding Expiration, and Default Expiration.

Absolute Data Expiration
Explains how to perform operations using Absolute Expiration.

Sliding Data Expiration
Explains how to perform operations using Sliding Expiration.