I love PostgreSQL but many of the tools for it are nowhere near the same level of quality as PostgreSQL itself. Many of the past start-ups have used MySQL and w

I love PostgreSQL but many of the tools for it are nowhere near the same level of quality as PostgreSQL itself. Many of the past start-ups have used MySQL and whilst the base may not be as good the tooling on top makes their replication setups far simpler. I've given up on using an explicit load balancer (pgpool scales badly and is temperamental as you write). The application itself now handles load balancing, swapping out database connectors depending on whether it requires writes / no-lag reads. The current replicated PostgreSQL setup I have uses WAL-E for continuous archiving / backup (it recently got support for non-US-East S3 buckets[1]) and repmgr for replication management (hasn't seen a release in a year and the documentation is somewhat sparse). Don't get me wrong, I like and respect both projects, but I have less confidence in and more complications from them than PostgreSQL. [1]: https://github.com/wal-e/wal-e/pull/3 https://github.com/wal-e/wal-e/pull/3