Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Explain what a standby system is, and how it differs from the backups covered on the previous page.
- Explain how a standby stays in sync by continuously receiving the write-ahead log.
- Explain what failover is, and what can go wrong during it.
- Explain the cost trade-off between synchronous and asynchronous replication to a standby.
The previous page covered backups: a point-in-time snapshot that has to be actively restored, taking real time, after a failure. This closing page of the level covers a system designed to make that restore unnecessary in most cases. A standby is already running, and already nearly caught up, before a failure even happens.