PostgreSQL High Availability Options

Let’s review several popular solutions that increase the high availability of PostgreSQL deployments and, as a result, the overall application. It is shown how to approach the high availability for the following four PostgreSQL deployment scenarios: 1. Single primary database instance 2. Single primary database instance with read replicas 3. Multi-master deployment (sharded PostgreSQL with a coordinator, e.g. CitusData) 4. Multi-master (sharded PostgreSQL without the coordinator, e.g. YugabyteDB) To learn more, read our guide to PostgreSQL high availability options: https://www.yugabyte.com/postgresql/postgresql-high-availability/ 0:00 - Intro 0:31 - Widespread PostgreSQL deployment options 1:38 - High availability (HA) vs. disaster recovery 2:23 - HA with a single PostgreSQL database instance 6:34 - HA with a single primary instance and read replicas 8:04 - Sharding and horizontal scalability 9:06 - HA with multi-master deployments with coordinator (e.g. CitusData) 12:40 - HA for multi-master deployments without coordinator (e.g. YugabyteDB) 16:08 - Summary RESOURCES: -YugabyteDB / Start Now: https://cloud.yugabyte.com -Site: https://www.yugabyte.com -GitHub: https://github.com/yugabyte COMMUNITY: -Slack: https://communityinviter.com/apps/yugabyte-db/register -YouTube: https://www.youtube.com/c/YugaByte -Instagram: https://www.instagram.com/yugabytedb/ -Twitter: https://twitter.com/yugabyte -LinkedIn: https://www.linkedin.com/company/yugabyte You can connect to all our community channels here: https://linktr.ee/yugabyte