database

Sequence a compatible column migration, reconcile concurrent writes, and identify when returning to the old application starts requiring data repair.

An idle database with a starved application is the tell. The connections are held, not used. More database capacity does not release leaked connections.

Split-brain writes are a fencing failure first and a data problem second. Freeze writes, read the divergence boundary from replication positions, and let the payment ledger arbitrate reality.

Every candidate says replication and failover. The scoring answer names the replication mode, states the resulting data loss window, and explains how the cluster avoids two primaries.