yurykovshov

Simple Postgres Database deployment with PgBouncer connection pool and backups to S3 storage

Motivation and Goal

Main motivation here is to have a cheap and simple Postgres Database server with backups, but without the failover. And in order to get cheap (in terms of memory) connections - use the PgBouncer. Why without the failover? Because in my case I didn't need a 100% stable cluster, but I needed a cheap and simple solution, which in case of disaster could be recovered in some X hours. If you are looking for a failover cluster - there is nice automation here: https://github.com/vitabaks/postgresql_cluster

Prerequisites

yurykovshov

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

yurykovshov

Шаг 1 - Купить свой виртуальный сервер

Можно в любом хостере за пределеами России:

• http://hetzner.de
• https://www.digitalocean.com/ и т.п.

Например, можно взять самый простой Cloud VPS на Hetzner: https://www.hetzner.de/cloud CX11 за 2,5 евро в месяц.