<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PaxosLease: Diskless Paxos for Leases · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1209.4187/</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/1209.4187/feed.xml" rel="self" type="application/rss+xml" /><item><title>PaxosLease: Diskless Paxos for Leases — mentioned by Maro</title><link>https://news.ycombinator.com/item?id=41431376</link><guid isPermaLink="false">urn:hackerpapers:mention:1209.4187:41431376</guid><pubDate>Tue, 03 Sep 2024 04:50:35 GMT</pubDate><description>&lt;p&gt;I think a lot has changed since 2013 when this article was written. Back then cloud services were less mature and there were more legitimate cases when you had to care about the theoretical distributed aspects of your backend architecture.. although even then these were quickly disappearing, unless you worked at a few select bigtech companies like the FAANGs. But today, in 2024, if you just standardize on AWS, you can pretty much use one of the AWS services for pretty much anything. And that AWS service will be already distributed in the backend, for free, in terms of you not having to worry…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1209.4187/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item><item><title>PaxosLease: Diskless Paxos for Leases — mentioned by erichocean</title><link>https://news.ycombinator.com/item?id=6888666</link><guid isPermaLink="false">urn:hackerpapers:mention:1209.4187:6888666</guid><pubDate>Wed, 11 Dec 2013 16:50:56 GMT</pubDate><description>&lt;p&gt;And if you&amp;#x27;re considering Paxos, PaxosLease[0] is a nice, fast variation that&amp;#x27;s much less complex to actually implement in a production setting, and doesn&amp;#x27;t require co-ordinated clocks (clocks only need be consistent—monotonic—locally). It&amp;#x27;s amazing how far you can get with a reliable leader election protocol in a distributed system. We&amp;#x27;re getting to the point where all of the other stuff is just picking specific algorithms with specific tradeoffs, much like you do today in a non-distributed setting. [0] http://arxiv.org/pdf/1209.4187.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1209.4187/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
