Earlier quoted context omitted.
Not losing transactions with a database is not exactly terra incognita. > Because without distributed strict serializability Depends what you mean by "distributed". A simple 2-phase commit would do it. Or hell, just a write-ahead log on the application layer. > Postgres just doesn't seem like the best way to get distributed failover safely That may be so. But are you arguing in favour of blockchain? When was the last…
"But are you arguing in favour of blockchain?" No, please see my original comment, where I made this clear: "I don't mean to advocate for cryptocurrency in any way." By "modern distributed database", I don't mean blockchain. I just mean "modern distributed database", e.g. things like FoundationDB, Spanner, Aurora or CockroachDB. "A simple 2-phase commit would do it. Or hell, just a write-ahead log on the application…
I'm also excited about the modern distributed databases. They're pretty awesome.
But yeah, a HN comment is not the right place to design a resilient DB setup. Like I said it's not terra incognita, but it's also not just "spin up a postgres".