Cache invalidation
Cache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
Cache invalidation means treating a stored entry as no longer usable, for example by removing it or requiring another validation. Data changes or defined validity rules can trigger it.
An address change example
In a hypothetical portal, a customer company's delivery address changes. An earlier cached copy cannot serve indefinitely as the current address. The design must determine which copies are affected and how they are renewed.
An expiry rule alone does not automatically provide immediate agreement with the source. Concurrent fetches can also affect renewal. Deleting a cache entry does not remove the authoritative record either. Invalidation, updating the source and authorisation remain different tasks.
Sources
Related terms
- CachingCaching reuses stored data or results. Validity and the permitted user scope belong in the design.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
- Master dataMaster data describes core business entities such as customers or products. It is reused across processes and can still change over time.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- ThroughputThroughput describes work processed per period. It is neither the duration of one request nor the number of concurrent users.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps