Tools & Integration · Data artifact
Cache Invalidation Policy
Data artifactTools & IntegrationOrchestration & ToolsVariation point (abstract)arc:CacheInvalidationPolicy
An abstract configuration deciding when cached tool results become stale and must be refreshed, balancing result freshness against latency and cost savings.
Responsibility. Determines when cached tool results are invalidated.
Also known as: Cache freshness policy
Variants
| Variant | When to choose |
|---|---|
| Event-Based Cache Invalidation Policy | Choose when the upstream source can signal publication of updates, so freshness need not wait for a TTL. |
| Time-Based Cache Invalidation Policy | Choose when the source updates on a known schedule and no change notifications are available. |
Relationships
constrains control
Design guidance
- SHOULD cache a tool only when call frequency exceeds result volatility (e.g., daily-updated search: cache; real-time stock prices: do not cache).
Classification
- Patterns
- MemoizationFrequency-vs-volatility caching decision
- Quality attributes
- Functional suitability: correctness and validity (ISO/IEC 25010 | NIST AI RMF: valid)Performance efficiency (ISO/IEC 25010)
- Risks mitigated
- Serving stale tool results
Sources
- Ch7.3: T. Nguyen, "NeMo Agent Toolkit Profiling," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 7.3. ISBN: 9798244538229.