spilo

Highly available elephant herd: HA PostgreSQL cluster using Docker

Explore on GitHub Read Hacker News discussions

7Distinct people

8Mentions

0Explicit recommenders

1.9KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Highly available elephant herd: HA PostgreSQL cluster using Docker

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

patroni/patroni · linked in 5 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year8 dated mentions

Observed mentions: 2017-02-26 19:07:11 UTC to 2024-06-10 22:06:23 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	3	0	3
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	2	0	2
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1	0

What Hacker News says

2 sources

DasIch·Dec 31, 2018

Spilo[1] is a Docker image that provides postgres bundled with Patroni[2]. The postgres-operator I linked earlier but also our setup on AWS (with one image per EC2 instance) uses that to actually run Postgres. [1]: https://github.com/zalando/spilo [2]: https://github.com/zalando/patroni

In KubeDB – Run production-grade databases easily on Kubernetes

merb·May 30, 2018

well you actually should be a little bit more familiar with all the concepts of the system to do the stuff. what do you use to scale your databases: databases can be scaled with statefulsets there is a good library that helps with that: github.com/zalando/spilo it is actually way easier than scaling over vms (especially on bare metal) since 1.10 you can even use block storage with local storage, so no need for a storage system. so basically k8s is just a good layer to scale such things, before we used patroni without k8s and it is way harder to actually do service discovery (more on that later) what do you use for master election: master election can be done with configmap or endpoints (actually github.com/zalando/spilo uses github.com/zalando/patroni for running postgresql and does master election over endpoints or configmap annotations)

Read the rest

actually etcd also exists when you use k8s (actually it's the hardest thing to install when you deploy k8s) what do you use to deploy your stuff: well deployment/apps are extremly easy to use and do zero downtime deployments when you just change your image version what do you use on the tcp level for HA (keepalived?): some folks at google created metallb: https://metallb.universe.tf/ it's actually a load balancer on top of k8s that is so simple to use (just run https://metallb.universe.tf/tutorial/layer2/ and it will work) what do you use to keep your system up to date: well that's more tricky however ContainerLinux (formerly CoreOS) (not related to k8s) works very well for keeping the os up to date. you can even use https://github.com/coreos/container-linux-update-operator to only update one node at the time in a k8s env. however it also works without k8s, but you still need to run mostly container software on ContainerLinux. If you are new to k8s and want to know more about "easy" to use on bare-metal stuff you should look into ContainerLinux ignition and kubeadm, it's really simple to get up and running from scratch, it's mostly just creating a nice cloud-config and run kubeadm once on the nodes you wanna install.

In Will Kubernetes Collapse Under the Weight of Its Complexity?