Expert
The database that moved
Last Tuesday on staging, a worker rebooted and all the orders vanished, then new ones appeared out of nowhere (ops/staging-incident.md). Production runs the same stack.yaml, with 48 210 real orders. A node will fail one day: when it happens, the shop may be unavailable while the node is down (database replication is next quarter's project), but it must never lose an order.
Your terminal is on manager-1 (drained). The test calls http://<cluster>/products every minute and creates an order (POST /orders) every five minutes, for two hours. At 0:30, the node that runs the database loses power for fifteen minutes. At the end, the orders are counted.
What your server must hold
- No record lost
- Availability ≥ 80 %