Why this matters
- A regional AWS outage without a tested failover plan means VaultCommerce cannot process checkouts — revenue stops and carts abandon.
- Interviewers ask you to define RPO/RTO, then walk through how Postgres PITR and Redis persistence map to each.
- Backups you have never restored are Schrödinger's backups — VaultCommerce runs quarterly restore drills into an isolated VPC.
RPO and RTO for VaultCommerce
Targets by data tier
- Orders and payments (Postgres) — RPO 5 minutes, RTO 30 minutes. Achieved with continuous WAL archiving plus cross-region read replica promoted on failover.
- Sessions and cart cache (Redis) — RPO 1 minute, RTO 10 minutes. AOF with
appendfsync everysec; accept sub-second loss on catastrophic node failure. - Product search (Elasticsearch 8) — RPO 15 minutes, RTO 45 minutes. Snapshot to S3 every 15 minutes; search is rebuildable from Postgres if snapshots fail.
- Analytics events (DynamoDB) — RPO 0 with PITR enabled; RTO 60 minutes for table restore into a new region.
RPO answers: "If the database vanishes right now, how many minutes of writes are gone?" RTO answers: "How long until checkout works again?"
Postgres 16 backup stack
VaultCommerce runs RDS PostgreSQL 16 with automated backups and WAL archiving to S3.
-- Verify PITR window (RDS: retention set in console; self-managed: archive_command)
SELECT pg_switch_wal();
SELECT * FROM pg_stat_archiver;
Automated snapshots — daily full backup; retention 35 days.
Continuous archiving — WAL segments shipped to S3 every 60 seconds; enables point-in-time recovery to any second within the window.
Logical backups — weekly pg_dump of schema-only for migration testing; not used for production restore (too slow at 400 GB).
# Restore to a specific timestamp (self-managed example)
pg_restore --dbname=vaultcommerce_recovery \
--target-time="2026-09-15 14:32:00+00" backup_manifest
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Cross-region failover
- Redis 7 persistence for DR
- Elasticsearch snapshot recovery
Test yourself
Answer these before moving on — recall is what makes it stick.