Hacker News with Generative AI: High Availability

PostgreSQL High Availability Solutions – Part 1: Jepsen Test and Patroni (binwang.me)
I’ve used Cockroach DB for a few my side projects. I enjoyed it overall. But since it announced license change and require mandatory telemetry collection for free version, I started to look for alternatives. The most nature chose is to just use the plain old PostgreSQL since my data size is not that big and even a less powerful machine can handle it without any problem.
Categorizing How Distributed Databases Utilize Consensus Algorithms (medium.com)
Distributed databases generally fall into two camps when it comes to architectures for maintaining high availability (HA) [1]. Both architectures are used by many successful production systems, but each has very different trade-offs. I couldn’t find anyone who had studied these trade-offs, which is what motivated this article. I don’t know of standard/well-known names for the two HA approaches, so I’m going to refer to them as “Consensus for Metadata” (CfM) and “Consensus for Data” (CfD).
PostgreSQL Streaming Replication (WAL); What It Is and How to Configure One (mindhub365.com)
Streaming replication in PostgreSQL is an efficient method for maintaining a near real-time replica of a primary database on one or more standby servers.
Why do systems fail? Tandem NonStop system and fault tolerance (erlang-solutions.com)
Why do systems fail? This question should probably be asked more often, considering all the factors it involves. It was central to the NonStop architecture because achieving high availability depends on understanding system failures.
High Availability, Zone-Aware Load Balancing (buoyant.io)
Spilo: High Availability PostgreSQL cluster using Docker (github.com/zalando)