postgresql_cluster VS pg_auto_failover

Creating a robust and reliable database cluster is often fraught with challenges.A manual deployment process can be fraught with risks, particularly for those who lack extensive experience. Even minor errors in configuration can drastically affect your database's performance and stability.

Recognizing this intricacy, many businesses choose to use cloud-based managed databases. These services offer convenience but not without limitations. These drawbacks can include being tied to a specific cloud provider and limited direct access to the database server for adjustments. These constraints can hinder your ability to tune your system and perform thorough performance analyses.

In response to these challenges, we've developed a project to make this process easier and more efficient. This project uses automation to streamline the deployment of High-Availability PostgreSQL Clusters. By doing so, it helps mitigate the risks involved with manual configuration and speeds up the deployment process.

Our solution caters to various deployment environments. It allows you to establish your cluster either in your own data center or in the cloud, providing a robust database solution similar to managed databases, but with you retaining full control.

Explore the project here: https://github.com/vitabaks/postgresql_cluster

FYI: postgresql_cluster

HA postgres

If not Kubernetes, check out this: https://github.com/vitabaks/postgresql_cluster – Postgres + patroni + pgBouncer + WAL-G or pgBackRest + Netdata + more, managed by Ansible.

If you do want to use Kubernetes, then check out StackGres.io and https://github.com/zalando/postgres-operator

Also check PostgreSQL High-Availability Cluster (based on "Patroni" and "DCS(etcd)"). Automating deployment with Ansible.

pg_auto_failover makes it an absolute breeze. I cannot understand how it's not mentioned in the article.

I've been runnning it for 3 years with great success - https://github.com/hapostgres/pg_auto_failover/discussions/6...

Simplified and probably OK: pg_auto_failover - One Monitor/Witness node and minimum services otherwise. Good documentation to get started and not nearly as complex as Patroni.

This is /extremely/ uncharitable. It depends more on the project.

For example, both Go and .NET are very well written with comprehensible documentation. Many projects have also been absorbed by the Apache Foundation or other FOSS initiatives.

Every FANG has boat loads of teams working on umpteen different open source packages. The quality naturally varies.

Let me pick two more esoteric projects as a point of comparison.

Yandex Odyssey (https://github.com/yandex/odyssey) an advanced multi-threaded PostgreSQL connection pooler and request router. Figuring out how exactly and when to use this is not quite clear. There is no "getting started" guide for this package. There is barely any explanation for how it works or what it does.

pg_auto_failover (https://github.com/citusdata/pg_auto_failover) run by Citus (owned by Microsoft) monitors and manages automated failover for a Postgres cluster. This repo even has diagrams explaining the workflow and complete instructions.

I completely missed the news that Microsoft acquired Citrus back in 2019.

I noticed in their MIT like license it referred to Microsoft and way confused until I learned they were acquired.

https://github.com/citusdata/pg_auto_failover/blob/master/LI...

Not multi-master, but pg_auto_failover looks to be a very nice solution for HA, and one that is operationally simple to manage: https://github.com/citusdata/pg_auto_failover

Also check https://github.com/citusdata/pg_auto_failover