Expand description
Replication for the FixedStore backend.
Separate module from crate::replication (Bitcask). Separate port,
protocol, and lifecycle. See
armdb/docs/superpowers/specs/2026-04-17-fixed-replication-design.md.
Re-exports§
pub use apply::ApplyOutcome;pub use apply::FixedReplicationTarget;pub use client::FixedReplicationClient;pub use cursor::FixedReplicationCursor;pub use engine_access::ArcEngine;pub use engine_access::FixedEngineAccess;pub use event::FixedReplicationEvent;pub use server::FixedReplicationServer;
Modules§
- apply
- Follower apply trait. Concrete impls for ConstTree
and ConstMap live in Tasks 22-23. - client
- Follower-side replication client for FixedStore.
- cursor
- Per-shard diagnostic cursor for the FixedStore replication follower.
- engine_
access - Trait abstracting the leader engine for the replication server.
Lets tests mock engine behavior and keeps server code decoupled
from
FixedEngine. - event
- SPSC event payload pushed by leader’s write_slot / delete_slot and consumed by the replication server.
- protocol
- Wire protocol for FixedStore replication.
- server
- Leader-side replication server for FixedStore.