The issue with “no good solution” is that sometimes things are inherently hard and certain technologies don’t permit lying. Good example is async in Rust; peop

The issue with “no good solution” is that sometimes things are inherently hard and certain technologies don’t permit lying. Good example is async in Rust; people don’t like it but mostly because async is hard. Postgres has excellent HA options, if you know what you’re trying to do with your data. CitusDB for data-warehousing storage, TimescaleDB for time-series data, and the traditional replication system for having HA (with a single write-primary) - which is the same method that Elasticsearch and ETCd are doing under the hood. Though in Elasticsearches case they do it by aggressively sharding their data set and splitting write masters across multiple nodes which has huge latency tradeoffs. Other multi-master HA systems have trade offs (or, lie about not having tradeoffs *cough* mongo *cough*).