<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Conflict-free Replicated Data Types: An Overview · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1806.10254/</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/1806.10254/feed.xml" rel="self" type="application/rss+xml" /><item><title>Conflict-free Replicated Data Types: An Overview — mentioned by maffydub</title><link>https://news.ycombinator.com/item?id=30985954</link><guid isPermaLink="false">urn:hackerpapers:mention:1806.10254:30985954</guid><pubDate>Mon, 11 Apr 2022 08:07:04 GMT</pubDate><description>&lt;p&gt;I believe that Redis supports CRDTs (https://redis.com/blog/diving-into-crdts/) for its active/active geo-replication, and they&amp;#x27;re supposed to be pretty fast. ...but it&amp;#x27;s important to note that CRDTs as used by Redis (and as defined by, for example, https://arxiv.org/pdf/1806.10254.pdf) really just means that you&amp;#x27;ve defined a way to consistently resolve conflicts - it doesn&amp;#x27;t necessarily mean the all-singing-all-dancing collaborative text editing that a lot of people seem to be assuming. For example, as defined in the paper above, simple &amp;quot;last write wins&amp;quot; is a CRDT.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1806.10254/"&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>Conflict-free Replicated Data Types: An Overview — mentioned by maffydub</title><link>https://news.ycombinator.com/item?id=30985917</link><guid isPermaLink="false">urn:hackerpapers:mention:1806.10254:30985917</guid><pubDate>Mon, 11 Apr 2022 08:01:33 GMT</pubDate><description>&lt;p&gt;Slightly pedantic, but I think you&amp;#x27;ll actually find that all of these are CRDTs. If you read &amp;quot;Conflict-free Replicated Data Types: An Overview&amp;quot; (https://arxiv.org/pdf/1806.10254.pdf), it refers to both last write wins and &amp;quot;record all versions of the data&amp;quot; as CRDTs in 2.1.1. My understanding is that &amp;quot;CRDT&amp;quot; really just means that you&amp;#x27;ve defined how you&amp;#x27;re going to resolve conflicts consistently (see criteria in s2.2 of the paper above).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1806.10254/"&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>
