Files
mytheclipse/crates/mytheclipse-cache
asepharyana 901fc51f7b fix(cache): align redis dep to 0.32 for deadpool unification
Scraper uses deadpool-redis 0.22 (redis 0.32). mytheclipse-cache pinned
redis 0.27, forcing two redis crate versions in the resolver and making
RedisCache's MultiplexedConnection incompatible with deadpool's.
Bump to 0.32 so consumers can pass a deadpool Connection via take().
2026-08-30 18:52:46 +07:00
..

mytheclipse-cache

A unified multi-layer cache abstraction so your app isn't locked to one cache provider. Combines an in-process L1 cache with a distributed L2 cache (e.g. Redis/Valkey) behind one simple get/set/invalidate API, plus a cache-aside / auto-refresh helper.

Features

  • l1-memory (default) — zero-dependency in-process cache.
  • l1-moka — high-performance Moka-backed L1 with TTL/max-capacity.
  • l2-redis — Redis/Valkey L2 via fred.
  • cache-aside (default) — read-through cache-aside helper.

Usage

use mytheclipse_cache::{Cache, MemoryCache, MultiLayerCache, CacheAside};

let cache = MultiLayerCache::new(
    MemoryCache::new(),          // L1
    MemoryCache::new(),          // L2 (use RedisCache in production)
);
cache.set("k", b"v".to_vec(), None).await.unwrap();
let v = cache.get("k").await.unwrap();

// Cache-aside: fill misses from a source of truth.
let aside = CacheAside::new(
    MemoryCache::new(),
    |key| async move { Some(format!("data-for-{key}").into_bytes()) },
);
let _ = aside.get("orders:42").await.unwrap();