RM
DATABASE / INFRASTRUCTURE DISASTER RECOVERY

RecoveryMesh

NORMAL
LIVE TOPOLOGY

Active / Standby Database Architecture

LIVE
⇢
Shipment APIReal application traffic
↓
R
Recovery RouterRouting writes to PRIMARY
HEALTHY
DB
PRIMARY PostgreSQL :5432
0 records
ACTIVE
replication
HEALTHY
DB
SECONDARY PostgreSQL :5433
0 records
STANDBY
ACTIVE SITEPRIMARYNormal operations
LAST RTO—Recovery time objective
REPLICATION LAG0record delta
QUEUED WRITES0protected during failover
TRANSACTIONS0accepted by mesh
FAILOVERS0automatic site switches
REAL TRAFFIC

Shipment Intake

Transactions will be written to the currently active database.
FAILURE LAB

Break it. Recover it.

System initialized
DATA CONSISTENCY

Recent Transactions

IN SYNC
ShipmentRouteAccepted ByPrimarySecondary
No transactions yet.
INCIDENT TIMELINE

Recovery Events

Waiting for events…
Portfolio DR Lab. The public demo intentionally co-locates both PostgreSQL nodes in one ephemeral runtime to keep hosting inexpensive. The reference architecture treats PRIMARY and SECONDARY as separate failure domains.