kape-memory
Process-local in-memory adapter for Kape.
[]
= "0.1.0"
= "0.1.0"
use MemoryBackend;
let backend = new;
The capacity is a maximum entry count, not a freshness guarantee: capacity eviction may remove a value before its TTL expires. TTL is only an upper bound on freshness.
Values remain typed and are stored as Arc<V> without serialization. Finite
expiry uses a private monotonic clock and Moka's per-entry expiration policy.
Expired entries are returned as misses and become eligible for removal during
Moka's lazily driven maintenance tasks. An idle cache does not run a dedicated
cleanup thread. Moka is a private implementation detail.
Clones of one backend share storage. Separately constructed backend instances
are isolated, and clear affects only the instance on which it is called.