Skip to content

Instantly share code, notes, and snippets.

@drnic

drnic/abstract-ha-postgresql-patroni-docker.md

Last active March 23, 2016 00:24
Show Gist options
  • Save drnic/6099848277df08ea3280 to your computer and use it in GitHub Desktop.
Save drnic/6099848277df08ea3280 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
abstract-ha-postgresql-patroni-docker.md

Orchestrating high-availability PostgreSQL in 2016 - Patroni, wal-e & Docker

PostgreSQL can be the only database you need - it offers SQL and NoSQL/JSON, it supports high-availability via synchronous or asynchronous replication to followers, and supports disaster recovery by storing backups and incremental write-ahead logs (WAL) offsite. But orchestrating all this is not easy; and can be a major engineering effort by DBAs or DevOps teams to build out and maintain. And that's just for one database. What if you want hundreds or thousands?

Fortunately in 2016 we have solutions. Patroni [1] is a major step forward in making it easy to setup a highly available PostgreSQL cluster. wal-e [2] provides a way to store base backups and progressive WAL updates offsite in AWS S3, Azure or similar. Docker [3] makes it easy to provision many isolated PostgreSQL services across a shared fleet of pre-provisioned machines.

In 2016, highly-available, disaster proof PostgreSQL may be easier to provision than not to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment