Faultline

What happens when your database backup fails too?

When both your primary database and its backup fail simultaneously, every service that reads or writes data goes down. In a simulated dual-database failure (AWS RDS + GCP Cloud SQL) across 18 interconnected services, 6 services failed completely and 2 degraded, with an estimated revenue impact of $600,000+ over 6 hours. Transaction ledgers become unavailable, user accounts can't be accessed, compliance systems go offline, and payment processing halts.

Studies show about 25% of database failovers don't work as expected during real outages. Use the interactive simulator below to trigger this worst-case scenario and watch the cascade unfold.

[Interactive simulator loads here — requires JavaScript]

Expected Impact Summary

When this scenario is triggered, the cascade engine traces every dependency path and calculates the full blast radius. Here's what happens to the 18-service infrastructure over 6 hours:

Cascade order: AWS RDS Primary → GCP Cloud SQL → Transaction Ledger → User Account Service → Compliance Engine → Payment Processing → Reporting & Analytics → Fraud Detection

This simulation is powered by Faultline's dependency mapping and cascade analysis engine — the same engine you can use on your own infrastructure. Get early access to map your services, run your own simulations, and identify single points of failure before they cause real outages.

Frequently Asked Questions

How common are failed database failovers?

More common than you'd think. Studies show that about 25% of database failovers don't work as expected during real outages, often due to replication lag, configuration drift, or untested failover procedures.

How do I test database failover?

Regular chaos engineering exercises, scheduled failover drills, monitoring replication lag, and using tools like Faultline to simulate the cascade impact before it happens in production.

Try Other Scenarios