<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>An algorithm for geo-distributed and redundant storage in Garage · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2302.13798/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2302.13798/feed.xml" rel="self" type="application/rss+xml" /><item><title>An algorithm for geo-distributed and redundant storage in Garage — mentioned by lima</title><link>https://news.ycombinator.com/item?id=46153362</link><guid isPermaLink="false">urn:hackerpapers:mention:2302.13798:46153362</guid><pubDate>Thu, 04 Dec 2025 21:29:43 GMT</pubDate><description>&lt;p&gt;Shipping updates almost weekly is the opposite of what I want for a complex, mission-critical distributed system. Building a production-ready S3 replacement requires careful, deliberate and rigorous engineering work (which is what Garage is doing[1]). It&amp;#x27;s not clear if RustFS is even implementing a proper distributed consensus mechanism. Erasure Coding with quorum replication alone is not enough for partition tolerance. I can&amp;#x27;t find anything in their docs. [1]: https://arxiv.org/pdf/2302.13798&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2302.13798/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DS</category></item></channel></rss>
