Database secondary failover

Hypothesis

The database fails over to the secondary node with:

1. No interruption in service,
2. No data loss,
3. No impact to our applications and services.

‍

Why run this Scenario?

Dependencies are unreliable and can fail at any time. This is especially true for databases. Do you know if your database will reliably failover when the primary instance fails? And how does your application tolerate this failover process if it's slow?

Running this Scenario helps you:

• Verify that your database cluster can reliably failover from a primary instance to a secondary.
• Detect incomplete or corrupt data due to slow replication.
• Verify that your application gracefully handles a temporary interruption in database access.