Answers: <p>I ended up using stolon for its automatic leader election and fail over handling.
  Crunchy Data offers small building blocks so there is a lot of work to do to put them all together while stolon has a ready helm chart.
  But I didn't try patroni since stolon worked just fine. </p>
  
Answers: CC BY-SA 4.0
Answers: 2018-12-25T17:09:37.577Z
Answers: 2018-12-25T17:09:37.577Z
Answers: Nouran S. Ahmad
Body: <p>I'm using <strong>helm</strong> charts with <strong>kubernetes</strong> and I'm trying to deploy High Availability Postgresql database and found this <a href="https://blog.lwolf.org/post/how-to-deploy-ha-postgressql-cluster-on-kubernetes/" rel="nofollow noreferrer">article</a> mentioning three project that provide HA Postgresql:</p>
  
  <p><strong>1- <a href="https://github.com/sorintlab/stolon" rel="nofollow noreferrer">Stolon</a></strong></p>
  
  <p><strong>2- <a href="https://github.com/CrunchyData/crunchy-containers" rel="nofollow noreferrer">CrunchyData</a></strong></p>
  
  <p><strong>3- Patroni</strong> </p>
  
  <p>I didn't find helm chart example for Patroni, but I installed both helm charts for Stolon and Crunchy. However, I wasn't able to find the differences between them except in the structure, both use statefulset from kubernetes in order to deploy master service and a number of replicas(ReadOnly slaves),stolon has this proxy service that points to the master service which is like an extra layer, makes the stolon look a little more complex than crunchy.</p>
  
  <p>But what I really need to know is:</p>
  
  <ol>
  <li>How the replicas will synchronize with the master? synchronous or<br>
  asynchronous.</li>
  <li>Whats the failover mechanism provided if any?</li>
  <li>persistence volumes why is there a volume per pod? How is this
  related to the replication?</li>
  </ol>
  
Comments: CC BY-SA 4.0
Comments: 2018-12-11T01:40:34.283Z
Comments: The Patroni helm is in incubator vs stable. helm install incubator/patroni. TG
Comments: CloudSlayer
Tags: <kubernetes><helm><postgresql>
Title: Stolon vs CrunchyData for HA Postgresql
UserDisplayName: Nouran S. Ahmad
ThreadText: # Stolon vs CrunchyData for HA Postgresql
  
  (Asked by: username_0 on 2018-09-05)
  
  I'm using **helm** charts with **kubernetes** and I'm trying to deploy High Availability Postgresql database and found this [article](https://blog.lwolf.org/post/how-to-deploy-ha-postgressql-cluster-on-kubernetes/) mentioning three project that provide HA Postgresql:
  
  **1- [Stolon](https://github.com/sorintlab/stolon)**
  
  **2- [CrunchyData](https://github.com/CrunchyData/crunchy-containers)**
  
  **3- Patroni**
  
  I didn't find helm chart example for Patroni, but I installed both helm charts for Stolon and Crunchy. However, I wasn't able to find the differences between them except in the structure, both use statefulset from kubernetes in order to deploy master service and a number of replicas(ReadOnly slaves),stolon has this proxy service that points to the master service which is like an extra layer, makes the stolon look a little more complex than crunchy.
  
  But what I really need to know is:
  
  1. How the replicas will synchronize with the master? synchronous or  
     asynchronous.
  2. Whats the failover mechanism provided if any?
  3. persistence volumes why is there a volume per pod? How is this
     related to the replication?
  
  **Tags:** kubernetes, helm, postgresql
  
  > **Comments:**
  > **username_1**: The Patroni helm is in incubator vs stable. helm install incubator/patroni. TG  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-12-25. Score: 2 | Accepted answer
  
  I ended up using stolon for its automatic leader election and fail over handling.
  Crunchy Data offers small building blocks so there is a lot of work to do to put them all together while stolon has a ready helm chart.
  But I didn't try patroni since stolon worked just fine.
  
  
  ---
  
  