view release on metacpan or  search on metacpan

docs/adr/0012-replicated-storage-in-core.md  view on Meta::CPAN

- Replicated storage is always available in core, loaded as one Schema component,
  with no optional-feature install and no Moose runtime pulled in.
- Read/write routing is owned here (writes/txns/deploy → master, reads →
  balancer, default `Balancer::First`); credential provision is *not* — that is
  the AccessBroker seam (ADR 0013). A replicant's credential never gates
  transactions; only the master's does (CONTEXT.md). The two concerns meet at the
  `HostBound` view (ADR 0013), which lets one credential identity serve every
  host in the topology.
- **Layout flag:** the karr ticket says "lib/DBIO/Storage Replicated." The real
  shape is a top-level `DBIO::Replicated::*` subsystem (ten modules), not a single
  `Storage/Replicated.pm`. The relocation out of `Storage::` is itself part of the
  decision (first-class, not a Storage plugin).
- Tested in `t/test/08_replicated.t`, with broker interaction in
  `t/access_broker/06-replicated-passthrough.t` (the seam to ADR 0013).