<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Consensus on Rik Kisnah - Blog</title><link>https://www.rik-kisnah.ai/tags/consensus/</link><description>Recent content in Consensus on Rik Kisnah - Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 11 May 2021 09:00:00 -0700</lastBuildDate><atom:link href="https://www.rik-kisnah.ai/tags/consensus/feed.xml" rel="self" type="application/rss+xml"/><item><title>Design a Distributed Lock</title><link>https://www.rik-kisnah.ai/teach/systems/design-a-distributed-lock/</link><pubDate>Tue, 11 May 2021 09:00:00 -0700</pubDate><guid>https://www.rik-kisnah.ai/teach/systems/design-a-distributed-lock/</guid><description>Only one process at a time may touch the thing. Easy on one machine. Across a network, the lock holder can die, pause, or believe it still holds the lock when it does not. Leases, fencing tokens, and the honest answer: a lock cannot make an unsafe operation safe.</description></item></channel></rss>