Caching System With Smart Invalidation

via “result caching with configurable ttl and eviction policies”

Self-hardening prompt injection detector with multi-layer defense.

Unique: Implements configurable in-memory caching with multiple eviction policies (LRU, LFU, FIFO) and per-request cache bypass options, allowing developers to balance latency, cost, and memory usage; cache key includes configuration state to prevent incorrect hits when settings change

vs others: More sophisticated than simple TTL-based caching by supporting multiple eviction policies and configuration-aware cache keys; reduces API costs for repetitive workloads without requiring external cache infrastructure

via “vault state caching with invalidation strategy”

Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing notes, tags, and frontmatter, acting as a bridge to the Obsidian

Unique: Implements LRU-based in-memory caching with TTL invalidation and manual invalidation on write operations, enabling fast repeated access to vault data without polling Obsidian REST API. Cache keys are based on operation parameters enabling fine-grained invalidation.

vs others: In-memory caching provides sub-millisecond latency for cached queries (vs 50-200ms for REST API calls), with automatic TTL-based invalidation ensuring eventual consistency. Manual invalidation on writes prevents serving stale data after updates.

via “in-memory-caching-with-time-based-invalidation”

MCP-NixOS - Model Context Protocol Server for NixOS resources

Unique: Implements simple time-based caching with configurable TTL (default 1 hour) in ChannelCache and NixvimCache classes, reducing latency for repeated queries without requiring external cache infrastructure. Cache keys based on query parameters enable efficient cache hits.

vs others: In-memory caching with time-based invalidation is simpler than external cache systems (Redis, Memcached) while providing significant latency reduction for typical usage patterns.

via “redis caching strategy with multi-layer cache invalidation”

A repository of models, textual inversions, and more

Unique: Implements a multi-layer caching strategy with different TTLs and invalidation patterns for different data types, optimizing for both hit rate and freshness. Event-based invalidation ensures caches are updated when underlying data changes, reducing stale data issues.

vs others: More sophisticated than simple full-page caching because it caches at multiple layers (API responses, queries, computed values) and uses event-based invalidation, though it requires careful design to avoid stale data.

via “intelligent-caching-with-content-hashing”

TypeScript bridge for recursive-llm: Recursive Language Models for unbounded context processing with structured outputs

Unique: Uses content hashing for automatic cache key generation rather than explicit cache management, enabling transparent caching without modifying application logic

vs others: More automatic than manual cache key management and supports distributed backends, whereas simple in-memory caches don't scale to multi-worker systems

via “tool result caching with ttl and invalidation”

WaniWani SDK - MCP event tracking, widget framework, and tools

Unique: Integrates caching as a first-class concern in the tool execution pipeline with metadata-driven cache policies, rather than requiring developers to implement caching manually in each tool handler

vs others: More maintainable than manual caching in tool handlers because cache logic is centralized and can be updated globally, while remaining simpler than building custom caching infrastructure

via “manual cache invalidation and refresh”

TTL cache wrapper for MCP tool handlers — powered by vurb.

Unique: Provides both synchronous invalidation and asynchronous refresh APIs, allowing developers to choose between immediate cache clearing and background re-execution

vs others: More flexible than TTL-only expiration because it enables event-driven cache management tied to application logic

via “caching-system-with-smart-invalidation”

Out-of-Core DataFrames to visualize and explore big tabular datasets

Unique: Implements dependency-aware caching that tracks operation dependencies and invalidates only affected cached results when mutations occur, with support for both in-memory and disk-based caching. This differs from simple memoization by understanding the full operation graph and maintaining cache coherency.

vs others: More intelligent than naive memoization (invalidates only affected results) and more efficient than recomputing all results, though adds complexity compared to stateless computation.