<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Placement on Nalar</title>
    <link>https://nalar.dev/tags/data-placement/</link>
    <description>Recent content in Data Placement on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/data-placement/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rendezvous Hashing Keeps Key Placement Stable as Nodes Change</title>
      <link>https://nalar.dev/rendezvous-hashing-keeps-key-placement-stable-as-nodes-change/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/rendezvous-hashing-keeps-key-placement-stable-as-nodes-change/</guid>
      <description>&lt;h1 id=&#34;rendezvous-hashing-keeps-key-placement-stable-as-nodes-change&#34;&gt;Rendezvous Hashing Keeps Key Placement Stable as Nodes Change&lt;/h1&gt;&#xA;&lt;p&gt;Distributed systems often need a deterministic answer to a placement question: given a key and a current set of nodes, which node owns the key? A simple modulo rule such as &lt;code&gt;hash(key) % N&lt;/code&gt; is compact, but changing &lt;code&gt;N&lt;/code&gt; can move a large fraction of keys at once.&lt;/p&gt;&#xA;&lt;p&gt;Rendezvous hashing, also called highest-random-weight hashing, uses a different rule. For each key, it computes a deterministic score for every eligible node and selects the node with the highest score. Adding or removing a node changes placement only for keys whose ranking is affected by that membership change.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
