Skip to content
RepoRanker
Kareem411

Kareem411/TriCache

Credits + grant $1LibraryLive in production

tricache is an extremely fast three-tier Node.js cache library. It serves warm reads at 2.81 million operations per second from a single thread — over 100× fast

The ultra-performance, unified caching engine for Node.js.⚡Zero-JSON binary cache for Node.js. 🛡️ Hard multi-tenant isolation, deterministic reservoir eviction, inlined WASM Bloom filters, and polymorphic hardware ciphers (GCM/CTR/XOR). 🚀

★4▲ 2 since joining⑂ 3TypeScriptPush 8d agoListed 4mo ago17 open issuesMIT

www.npmjs.com/package/tricache

  • TypeScript100.0%
View on GitHub

$1

$0.60 from converted credits; $0.40 granted by RepoRanker. Credits and grants are not card payments. This placement does not expire. Its rank holds until another repo spends more, and then this one moves down, never off. Taking the top of the board from here costs $18.

Report a problem

1 Review

TriCache is an impressively detailed Node.js caching library with a strong systems-engineering angle. The README goes far beyond a basic package intro: it documents a three-tier design with L1 memory, disk spill, and Redis/Valkey L2; adaptive eviction; Count-Min Sketch frequency tracking; Bloom filter miss detection; stale-while-revalidate; stale-if-error; thundering-herd prevention; tag invalidation; batch operations; TTL jitter; OpenTelemetry; Prometheus metrics; circuit breaker behavior; encryption; snapshots; OOM guard; serverless disk detection; Redis Cluster/Sentinel; worker-thread crypto offload; and benchmarks. As a developer using it, the quick-start API is approachable while still offering serious production knobs. I especially like that the README explains not just what features exist, but why they matter under load. The main improvement would be restraint and verification surfacing: the feature list is so large that new users may wonder which paths are battle-tested. A “recommended production config,” a “minimal safe config,” and a compatibility matrix for Node/Redis/serverless environments would help. I’d also keep benchmark methodology and regression tests highly visible because performance is a central claim. Overall, this is a highly ambitious library with unusually thorough documentation.