⚠ Scenario: Database failover

Database failover testing

The database fails over in 30 seconds. The app takes 20 minutes, because every connection pool is still pointed at the old primary. Find out which you have.

What happens

The primary is stopped or demoted.

A replica is promoted.

Applications must reconnect to the new primary.

What it proves

Check 1

Connection pools and drivers reconnect.

Measured live, recorded in your GameDay report.

Check 2

Writes are not lost during the switch.

Measured live, recorded in your GameDay report.

Check 3

Your error budget survives the gap.

Measured live, recorded in your GameDay report.

Questions

+ Which databases are supported?

Managed and self-hosted PostgreSQL, MySQL and common managed cloud databases, via scoped roles or the agent.

Safe by design

Runs only against infrastructure you have verified you own, with a blast-radius limit, a hard time limit and an abort button. Never against third parties.