<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: somerandom1</title><link>https://news.ycombinator.com/user?id=somerandom1</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 10 Oct 2026 02:21:16 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=somerandom1" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by somerandom1 in "Celld: Self-hosted, distributed Durable Objects"]]></title><description><![CDATA[
<p>Seeing something like this reminds me of Kleppmann's blog post: <a href="https://martin.kleppmann.com/2016/02/08/how-to-do-distributed-locking.html" rel="nofollow">https://martin.kleppmann.com/2016/02/08/how-to-do-distribute...</a>.<p>celld's README states "Object-storage compare-and-swap ensures that exactly one node owns a cell at a time," but I'm skeptical this actually holds at the point where data is written to storage - I had an AI skim through the code with me, and the actual segment writes looked like plain, unconditional PUTs with no epoch check.<p>In many cases, I think using Cloudflare's Durable Objects is probably the right call instead.</p>
]]></description><pubDate>Fri, 07 Aug 2026 03:29:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=49205618</link><dc:creator>somerandom1</dc:creator><comments>https://news.ycombinator.com/item?id=49205618</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49205618</guid></item></channel></rss>