GLOSSARY
Cache
A cache retains previously retrieved data or computed results for reuse; without appropriate refreshing, it can cause outdated information to appear again.
Faster access has a freshness limit
If several salespeople research the same public company profile, reusing an earlier result can avoid repeated work. For prices, delivery commitments or rapidly changing events, the same strategy carries more risk. A fast response may reflect information that is no longer current. Cached information therefore needs a validity period appropriate to its purpose. The source and retrieval time should remain visible so users can judge whether a fresh check is necessary. The right interval depends on the likelihood of change and the consequences of acting on an outdated answer.
Reuse must respect access boundaries
Public information and customer-specific content require different rules. A cache must respect tenant isolation; similar questions from different customers do not justify sharing confidential responses. Retention and deletion also need to cover cached copies. A useful test changes a source fact or revokes access, then checks what the next request returns. This reveals whether the optimisation merely reduces waiting time or also propagates stale or unauthorised information. Assess the benefit after accounting for refresh and supervision effort.