> a single Postgres master with replication/standby gets you very far So does a distributed database. A primary/replica has an ops burden too, and measuring th

> a single Postgres master with replication/standby gets you very far So does a distributed database. A primary/replica has an ops burden too, and measuring that complexity is subjective. With primary/replica you still take downtime during failover, you need to make sure you're testing the failover, upgrades aren't zero downtime in a lot of cases, etc. You're essentially treating your database as a pet and a clustered option is much more cattle vs pet. This saves you time to develop other features (including working on reliability -- the most important feature)