https://hackerpaper.kaipfister.de/p/2607.13276/Collected HN comments and submissions linking this paper.enMon, 02 Nov 2026 11:16:22 GMThttps://news.ycombinator.com/item?id=49705479urn:hackerpapers:mention:2607.13276:49705479Mon, 14 Sep 2026 23:05:21 GMT<p>Basically, many people convinced themselves that the formalization of CAP means that systems need to choose between highly available and strongly consistent, and hence chose eventual consistency. This is, partially, because Gilbert and Lynch define &quot;availability&quot; to mean &quot;available to all clients, even those on a minority side of a partition&quot;. The much more useful &quot;available to a majority of clients&quot; is achievable at the same time as strong consistency in presence of a single partition, and this is the common cloud failure mode. See https://brooker.co.za/blog/2024/07/25/cap-again.html for a…</p><p><a href="https://hackerpaper.kaipfister.de/p/2607.13276/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.DBhttps://news.ycombinator.com/item?id=48951960urn:hackerpapers:submission:2607.13276:48951960Fri, 17 Jul 2026 20:31:12 GMT<p>Aurora DSQL: Scalable, Multi-Region OLTP</p><p></p><p>22 points; 2 discussion replies on HN. <a href="https://hackerpaper.kaipfister.de/p/2607.13276/">Paper and source history</a>. A submission is not an endorsement.</p>cs.DB