Deploying Highly Available, Durable Amazon RDS for PostgreSQL and for MySQL Databases
summary
Shows deploying Amazon RDS with one primary and two readable standbys across three AZs, using Postgres 13.4 or MySQL 8.0.28 on graviton instances with provisioned IOPS storage. Demonstration creates a cluster, runs a write-heavy workload, triggers failover and resumes operations with failover time around ~24 seconds. Reader endpoint load balances reads round robin between the two standbys, claim of up to 2x faster commit latency versus single-standby configurations.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:51Customize high availability for your workload's need
- 1:47Amazon RDS Multi-AZ with two readable standby DB instances
- 4:30Comparison of Multi-AZ options
- 5:34Amazon RDS Multi-AZ Semi Sync Replication
- 9:15Amazon RDS Multi-AZ Replica Lag
- 14:55Amazon RDS Multi-AZ with two readable standbys
- 15:40Amazon RDS Multi-AZ: Automatic failover scenarios
- 16:16Amazon RDS Multi-AZ with one standby: failover timeline
- 16:59Multi-AZ with two readable standbys: Read & Write endpoints
- 18:45Managing resources in Amazon RDS console
- 37:54Create Multi-AZ deployments in AWS CLI
- 40:20Amazon RDS availability options
- 44:04Next steps
related talks
41mRunning Highly Available Postgres in AWS RDS
14mBuilding a better PostgreSQL together
53mPostgres in Amazon RDS
54mBreakout Session
01h 05mDatabase management made simple - Amazon RDS (Part 1 and 2)
23mNew Amazon RDS innovations in 2022
40mPushing past PostgreSQL’s vertical scaling limits - Running Amazon RDS
37mNavigating Managed Databases for Over a Decade as a Non-DBA