All checks were successful
CI / verify (push) Successful in 2m33s
Add canonical operations/security/access/feature docs and fix path integrity to improve onboarding and incident readiness.
20 lines
504 B
Markdown
20 lines
504 B
Markdown
# ADR 0001: Peer Mesh Topology
|
|
|
|
## Status
|
|
|
|
Accepted
|
|
|
|
## Context
|
|
|
|
CBDDC requires local-first synchronization without a central coordinator in LAN-focused deployments.
|
|
|
|
## Decision
|
|
|
|
Adopt a peer mesh topology with gossip-based synchronization and per-node oplog tracking.
|
|
|
|
## Consequences
|
|
|
|
- Improves resilience when individual nodes disconnect.
|
|
- Requires strong operational tooling for lag, peer lifecycle, and pruning controls.
|
|
- Increases importance of clear runbook and troubleshooting documentation.
|