Monday
Sep162019
Managing High Availability in PostgreSQL – Part III: Patroni
Monday, September 16, 2019 at 12:31PM 
In our previous blog posts, we discussed the capabilities and functioning of PostgreSQL Automatic Failover (PAF) by Cluster Labs and Replication Manager (repmgr) by 2ndQuadrant. In the final post of this series, we will review the last solution, Patroni by Zalando, and compare all three at the end so you can determine which high availability framework is best for your PostgreSQL hosting deployment.
- Managing High Availability in PostgreSQL – Part I: PostgreSQL Automatic Failover
- Managing High Availability in PostgreSQL – Part II: Replication Manager
- Managing High Availability in PostgreSQL – Part III: Patroni
Patroni for PostgreSQL
tagged DBA, Patroni, PostgreSQL Automatic Failover, Postgres, REST API, Replication Manager, database, developer, high availability, postgresql, python, sql in Appliction monitoring, Clustering, DevOps, Failure Analysis, Geo-distributed Clusters, Performance, Postgres, Python, administrator, best platform, cloud, cluster, database replication, deployment, enterprise architecture, framework, high availability, infrastructure, master-slave, open source, postgresql, sql, tutorial Tweet
DBA, Patroni, PostgreSQL Automatic Failover, Postgres, REST API, Replication Manager, database, developer, high availability, postgresql, python, sql in Appliction monitoring, Clustering, DevOps, Failure Analysis, Geo-distributed Clusters, Performance, Postgres, Python, administrator, best platform, cloud, cluster, database replication, deployment, enterprise architecture, framework, high availability, infrastructure, master-slave, open source, postgresql, sql, tutorial Tweet