jonnify·bcs /bcs/store

B4 · EchoStore

The declared near-cache.

EchoStore is Part IV: L1 ETS tables in front of the L2 Valkey systems already share. The cache is declared, not discovered; a read never enters the owner; a miss is one fill per herd; coherence is a two-identity message.

Three dives. The declared cache and its two tiers; the cache-aside read path and its single fill; coherence by mint-time version — the durable Graft floor beneath is B5.

EchoStore: a declared directory over L1 and L2. Select a part.
EchoStore directoryregister · spec · tables — declared, not discovered a callerhit: :ets.lookup L1 · in-process ETSpublic, read-concurrent — per node L2 · Valkey — ecc:{table}:idshared, hashtaggedmiss: fill→ the loader
readout · Select a part. EchoStore is the declared near-cache: registered tables over L1 in-process ETS and L2 shared Valkey, a hit caller-side, a miss filled.
§1

The three dives

each a leaf, the teaching

A chapter is three dives. Each dive is one idea with one figure you can take apart.

§2

The cache, in one law

echo_store · echo_store.ex

EchoStore is Part IV: the declared near-cache. L1 ETS tables sit in front of the L2 Valkey systems already share, and the cache is declared, not discovered — every table registers its kind, its TTL, and its coherence mode in a directory, and a cache absent from the directory does not exist. A read is a caller-side lookup that never enters the owning process; a miss is one fill per herd, coalesced onto a single flight; expiry is jittered so no cohort dies together; and coherence travels as a two-identity message — the name and the writer’s mint-time version — over a broadcast lane and a job lane. The durable floor beneath it, the Graft engine, is B5.

§4

The doors

the sibling courses
§4

References

sources · related

Sources

Related