<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Sqlite on Syed Anwaruddin</title>
    <link>https://syed-anwar-uddin.github.io/tags/sqlite/</link>
    <description>Recent content in Sqlite on Syed Anwaruddin</description>
    <generator>Hugo -- 0.145.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://syed-anwar-uddin.github.io/tags/sqlite/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an EASM in Rust: Bypassing SQLite Concurrent Locks with RAM Aggregation</title>
      <link>https://syed-anwar-uddin.github.io/posts/asm-architecture/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://syed-anwar-uddin.github.io/posts/asm-architecture/</guid>
      <description>&lt;h1 id=&#34;building-an-easm-in-rust-bypassing-sqlite-concurrent-locks-with-ram-aggregation&#34;&gt;Building an EASM in Rust: Bypassing SQLite Concurrent Locks with RAM Aggregation&lt;/h1&gt;
&lt;p&gt;As I wrap up my undergraduate computer science engineering degree, I’ve been researching how organizations monitor their network perimeter. The External Attack Surface Management (EASM) market is dominated by massive platforms built for the enterprise. They are incredibly powerful, but for Small and Medium Businesses (SMBs) or IT agencies managing a handful of &lt;code&gt;/24&lt;/code&gt; subnets, these tools are prohibitively expensive and overly complex.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
