<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Structures on Lorbic</title>
    <link>https://lorbic.com/tags/data-structures/</link>
    <description>Recent content in Data-Structures on Lorbic</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 16 Jun 2026 22:00:00 +0530</lastBuildDate>
    <atom:link href="https://lorbic.com/tags/data-structures/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Constructing Concurrent Inverted Indexes in Go</title>
      <link>https://lorbic.com/constructing-concurrent-inverted-indexes-in-go/</link>
      <pubDate>Tue, 16 Jun 2026 22:00:00 +0530</pubDate>
      <guid>https://lorbic.com/constructing-concurrent-inverted-indexes-in-go/</guid>
      <description>&lt;p&gt;I spent a Saturday afternoon benchmarking a concurrent inverted index and discovered that a single &lt;code&gt;sync.RWMutex&lt;/code&gt; starts to break down at roughly 4 concurrent readers. The degradation is not linear. It is not graceful. It is a cliff.&lt;/p&gt;&#xA;&lt;p&gt;The inverted index is one of the oldest data structures in information retrieval. It maps terms to the documents that contain them, forming the backbone of every search engine from Elasticsearch to Lucene to Google&amp;rsquo;s earliest prototypes. The data structure itself is simple. Making it fast under concurrent load is not.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
