Patroni is a mature, widely-adopted, and battle-tested open-source template for building highly available PostgreSQL clusters. It reliably automates leader election and failover using a distributed consensus store, making it a solid choice for production HA setups.
We have collected here some useful links to help you find out if Patroni is good.
Check the traffic stats of Patroni on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of Patroni on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of Patroni's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of Patroni on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about Patroni on Reddit. This can help you find out how popualr the product is and what people think about it.
Patroni 1.0 was released in 2016, i.e ~10 years ago. https://github.com/patroni/patroni. - Source: Hacker News / about 2 months ago
PG's internal wal-level replication? Primary to a read-replica, and then switch the read to become the primary. You'll have a bit of downtime while you stop connections on the original server, switch the new server to primary, and update your app config to connect to the new server. I believe that's a pretty standard way to provide "HA" postgres. (We use Patroni for our HA setup) - Source: Hacker News / over 1 year ago
Do you need HA, or do you want to minimize downtime? At work we have something like an "error budget", were we accept downtime but try to minimize it. As such we have two nodes with one floating ip and a shared disk. The switch over takes as long as stopping the database on the first node, starting up the database on the second one and switching over the ip. Stuff like kernel updates takes us <1 minute of... - Source: Hacker News / almost 2 years ago
> I think etcd is basically a k8s only project now I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes: https://github.com/apache/apisix/blob/master/docs/en/latest/FAQ.md#why-does-apache-apisix-use-etcd-for-the-configuration-center, https://github.com/zalando/patroni#patroni-a-template-for-postgresql-ha-with-zookeeper-etcd-or-consul (this one shows up on HN quite a... - Source: Hacker News / over 2 years ago
We have been using stolon + consul for years without issue in our swarm environments. It may also be possible with patroni. Source: about 3 years ago
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 (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... - Source: Hacker News / about 3 years ago
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. Source: over 3 years ago
General purpose: Patroni - Set up your own etcd + HAProxy + Patroni + Postgres components and it'll generally manage itself after that. Source: over 3 years ago
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? Source: over 3 years ago
This is why I always recommend using a postgres proxy so you can point it to different database servers as you stand them up. AWS does this by default but GCP doesnโt yet, so you have to have your own Postgres proxy (e.g https://github.com/CrunchyData/crunchy-proxy) or move to an HA Postgres setup like Patroni that has streaming replication (https://github.com/zalando/patroni). Source: over 4 years ago
Want a tool for increasing the durability of your DB? I suggest running postgres via systemd, or failing that, start-stop-daemon. To get even more robust, look in to something like setting up pgbouncer in front of haproxy in front of a set of read-only replica PG instances running in either logical or streaming replication. To get even MORE robust, I suggest Patroni for high-availability PG. Source: about 5 years ago
Do you know an article comparing Patroni to other products?
Suggest a link to a post with product alternatives.
Is Patroni good? This is an informative page that will help you find out. Moreover, you can review and discuss Patroni here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.