stolon-chart
Kubernetes Helm chart to deploy HA Postgresql cluster based on Stolon (by lwolf)
patroni
A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes (by zalando)
Our great sponsors
stolon-chart | patroni | |
---|---|---|
1 | 19 | |
105 | 6,212 | |
- | 2.1% | |
0.0 | 9.2 | |
over 3 years ago | 16 days ago | |
Smarty | Python | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stolon-chart
Posts with mentions or reviews of stolon-chart.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Lessons learned after migrating from Heroku to a Kubernetes cluster
I am using the Stolon Helm chart : https://github.com/lwolf/stolon-chart I was advised on the topic by the consultant I mentioned in the article. I am not 100% confident about managing the database ourselves, but so far so good... and I am very confident in Postgres overall so that balances the matter. Stolon itself seems stable and mature. We tried using Google CloudSQL first (we are hosted on GKE) but we decided against it in the end because our strategy is to be platform-independent and self-contained. Also, we ran into issues related to users, admins and the ability to create extensions (I can't exactly recall what it was, just that it was a bummer).
patroni
Posts with mentions or reviews of patroni.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-18.
-
Citus is not ACID but Eventually Consistent
Citus doesn't provide fault tolerance. Each shard is a monolithic PostgreSQL. To reduce downtime on failures, you can protect each shard with a standby database. As this is a complex configuration, Patroni can help. For this lab I'll use the Citus+Patroni docker-compose-citus.yml from https://github.com/zalando/patroni.git:
-
How to create postgres cluster in docker swarm?
We have been using stolon + consul for years without issue in our swarm environments. It may also be possible with patroni.
-
Why PostgreSQL High Availability Matters and How to Achieve It
one of the solutions which made it pretty simple for us to run postgresql in a ha environment (mostly in k8s, but works standalone as well) is zalandos patroni: https://github.com/zalando/patroni it's really solid and worked for us for a few years already.
or for k8s their operator: https://github.com/zalando/postgres-operator (docker image: https://github.com/zalando/spilo) we've also tried other operators which were easier to get started, but they failed miserably (crunchyrolls operator is basically based on the zalando one)
-
Docker: Patroni + HAProxy + Etcd + PgBouncer
Hello. I am currently using this docker-compose model from Zalando repository. It does not include PgBouncer in its architecture by default. I've been trying to find a containerized implementation involving Patroni, HAProxy, Etcd and PgBouncer. I didn't find anything solid so far.
-
Can someone share experience configuring Highly Available PgSQL?
General purpose: Patroni - Set up your own etcd + HAProxy + Patroni + Postgres components and it'll generally manage itself after that.
- Patroni Version 3.0.0 Released
- Any self hostable postgres clustering, replication and fail over system?
-
Postgresql HA using repmgr and Keepalived
I don't have a great answer for you except that it sounds like you are trying to create your own version of patroni. Is there a good reason to not just use patroni?
-
Testing Patroni strict synchronous mode 👉🏻 you must handle invisible commit and read split brain
git clone https://github.com/zalando/patroni.git cd patroni docker build -t patroni . docker-compose up -d
-
Any recommandation Postgres Operator ?
I actually used Patroni on Openshift in my company. To be update with the latest version we created our helm chart.
What are some alternatives?
When comparing stolon-chart and patroni you can also consider the following projects:
traefik-helm-chart - Traefik Proxy Helm Chart
pg_auto_failover - Postgres extension and service for automated failover and high-availability