<?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>Azathoth LLC</title>
    <link>https://azathothllc.com/</link>
    <description>Recent content on Azathoth LLC</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>contact@azathothllc.com (Azathoth LLC)</managingEditor>
    <webMaster>contact@azathothllc.com (Azathoth LLC)</webMaster>
    <lastBuildDate>Wed, 18 Nov 2026 10:00:00 +0000</lastBuildDate>
    <atom:link href="https://azathothllc.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://azathothllc.com/about/</link>
      <pubDate>Wed, 18 Nov 2026 10:00:00 +0000</pubDate><author>contact@azathothllc.com (Azathoth LLC)</author>
      <guid>https://azathothllc.com/about/</guid>
      <description>&lt;h1 id=&#34;about-azathoth-llc&#34;&gt;About Azathoth LLC&lt;/h1&gt;&#xA;&lt;p&gt;Azathoth LLC is an independent technology consultancy and software engineering lab. We partner with engineering organizations to architect distributed systems, streamline developer tooling, and build resilient web services.&lt;/p&gt;&#xA;&lt;h2 id=&#34;our-philosophy&#34;&gt;Our Philosophy&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Speed over bloat&lt;/strong&gt;: Modern computing has plenty of resources, but software bloat robs users of responsiveness and reliability. We prioritize fast, lean architectures.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Zero-dependency mindset&lt;/strong&gt;: Complex dependency trees introduce fragility, security vulnerabilities, and maintenance headaches. We build robust systems with standard libraries and verified toolchains.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Content first&lt;/strong&gt;: Whether on the web or in application design, user content and clarity come before superficial chrome.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;connect&#34;&gt;Connect&lt;/h2&gt;&#xA;&lt;p&gt;Get in touch with our team:&lt;/p&gt;</description>
      <content:encoded><![CDATA[<h1 id="about-azathoth-llc">About Azathoth LLC</h1>
<p>Azathoth LLC is an independent technology consultancy and software engineering lab. We partner with engineering organizations to architect distributed systems, streamline developer tooling, and build resilient web services.</p>
<h2 id="our-philosophy">Our Philosophy</h2>
<ul>
<li><strong>Speed over bloat</strong>: Modern computing has plenty of resources, but software bloat robs users of responsiveness and reliability. We prioritize fast, lean architectures.</li>
<li><strong>Zero-dependency mindset</strong>: Complex dependency trees introduce fragility, security vulnerabilities, and maintenance headaches. We build robust systems with standard libraries and verified toolchains.</li>
<li><strong>Content first</strong>: Whether on the web or in application design, user content and clarity come before superficial chrome.</li>
</ul>
<h2 id="connect">Connect</h2>
<p>Get in touch with our team:</p>
<ul>
<li>Email: <a href="mailto:contact@azathothllc.com">contact@azathothllc.com</a></li>
<li>Read our <a href="/blog/">Blog</a>, review our <a href="/privacy/">Privacy Policy</a>, or subscribe to our <a href="/index.xml">RSS feed</a></li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>Modern Static Tooling: Why Hugo Still Wins</title>
      <link>https://azathothllc.com/blog/modern-static-tooling/</link>
      <pubDate>Wed, 18 Nov 2026 14:30:00 +0000</pubDate><author>contact@azathothllc.com (Azathoth LLC)</author>
      <guid>https://azathothllc.com/blog/modern-static-tooling/</guid>
      <description>&lt;p&gt;The web development landscape has spent a decade chasing JavaScript-heavy server-side rendering and client-side hydration. Yet for content delivery, nothing matches the speed, security, and low operational overhead of static site generators.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-case-for-zero-dependency-toolchains&#34;&gt;The Case for Zero-Dependency Toolchains&lt;/h2&gt;&#xA;&lt;p&gt;Modern front-end tooling often introduces thousands of dependencies in &lt;code&gt;node_modules&lt;/code&gt;, creating fragile build pipelines and persistent security scan alerts. Hugo avoids this entirely:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Single Binary&lt;/strong&gt;: No runtime dependencies, no package managers, and no compilation step for the toolchain itself.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Millisecond Build Times&lt;/strong&gt;: Even sites with thousands of markdown files compile in fractions of a second.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Rock-Solid Reproducibility&lt;/strong&gt;: Builds produce deterministic static assets that can be served anywhere.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;build-and-deployment-lifecycle&#34;&gt;Build and Deployment Lifecycle&lt;/h3&gt;&#xA;&lt;p&gt;Static publication follows an unambiguous four-step lifecycle:&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>The web development landscape has spent a decade chasing JavaScript-heavy server-side rendering and client-side hydration. Yet for content delivery, nothing matches the speed, security, and low operational overhead of static site generators.</p>
<h2 id="the-case-for-zero-dependency-toolchains">The Case for Zero-Dependency Toolchains</h2>
<p>Modern front-end tooling often introduces thousands of dependencies in <code>node_modules</code>, creating fragile build pipelines and persistent security scan alerts. Hugo avoids this entirely:</p>
<ul>
<li><strong>Single Binary</strong>: No runtime dependencies, no package managers, and no compilation step for the toolchain itself.</li>
<li><strong>Millisecond Build Times</strong>: Even sites with thousands of markdown files compile in fractions of a second.</li>
<li><strong>Rock-Solid Reproducibility</strong>: Builds produce deterministic static assets that can be served anywhere.</li>
</ul>
<h3 id="build-and-deployment-lifecycle">Build and Deployment Lifecycle</h3>
<p>Static publication follows an unambiguous four-step lifecycle:</p>
<ol>
<li>Author content in clean Markdown with structured YAML/TOML frontmatter.</li>
<li>Compile templates, assets, and feeds with the <code>hugo</code> command.</li>
<li>Verify output integrity and links.</li>
<li>Push static artifacts to global CDN edge nodes.</li>
</ol>
<h2 id="pipeline-architecture">Pipeline Architecture</h2>
<p>The pipeline from raw markdown to global distribution is clean and direct:</p>
<figure>
  <img src="/images/pipeline.webp" alt="Hugo Static Build Pipeline" width="800" height="240" loading="lazy" decoding="async">
  <figcaption><p>From raw Markdown to edge CDN delivery in milliseconds.</p></figcaption>
</figure>
<h2 id="configuration-as-code">Configuration as Code</h2>
<p>Hugo sites configure cleanly via standard TOML. Here is a sample module and build configuration:</p>





<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-toml" data-lang="toml"><span class="line"><span class="cl"><span class="nx">baseURL</span> <span class="p">=</span> <span class="s2">&#34;https://azathothllc.com/&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nx">title</span> <span class="p">=</span> <span class="s2">&#34;Azathoth LLC&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nx">defaultContentLanguage</span> <span class="p">=</span> <span class="s2">&#34;en&#34;</span>
</span></span><span class="line"><span class="cl"><span class="nx">theme</span> <span class="p">=</span> <span class="s2">&#34;hugo-bearcub&#34;</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="p">[</span><span class="nx">markup</span><span class="p">.</span><span class="nx">highlight</span><span class="p">]</span>
</span></span><span class="line"><span class="cl">  <span class="nx">noClasses</span> <span class="p">=</span> <span class="kc">false</span>
</span></span><span class="line"><span class="cl">  <span class="nx">lineNos</span> <span class="p">=</span> <span class="kc">false</span></span></span></code></pre></div><h2 id="related-content">Related Content</h2>
<p>Learn more about our infrastructure principles in <a href="/blog/building-fast-systems/">Building Fast and Resilient Systems</a>, or check out the official <a href="https://gohugo.io/">Hugo Documentation</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Privacy Policy</title>
      <link>https://azathothllc.com/privacy/</link>
      <pubDate>Wed, 18 Nov 2026 10:00:00 +0000</pubDate><author>contact@azathothllc.com (Azathoth LLC)</author>
      <guid>https://azathothllc.com/privacy/</guid>
      <description>&lt;p&gt;We believe privacy on the web should be respected by default. This policy outlines exactly how Azathoth LLC handles data on &lt;strong&gt;azathothllc.com&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-short-version&#34;&gt;The Short Version&lt;/h2&gt;&#xA;&lt;p&gt;We do not track you, we do not profile you, and we do not sell or monetize your data. This site is completely static and private by design.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-we-do-not-do&#34;&gt;What We Do Not Do&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;No Cookies&lt;/strong&gt;: We set zero cookies. There are no session cookies, no preference cookies, and no advertising cookies.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;No Trackers or Analytics&lt;/strong&gt;: We do not use Google Analytics, Meta Pixel, or any client-side analytics scripts.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;No Third-Party Requests&lt;/strong&gt;: Every asset (fonts, stylesheets, images) is served directly from our own domain. When you load a page on this site, your browser never contacts a third party.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;No JavaScript&lt;/strong&gt;: This website runs without client-side scripts. We do not fingerprint your browser, probe your screen dimensions, or monitor your browsing behavior.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;what-we-collect&#34;&gt;What We Collect&lt;/h2&gt;&#xA;&lt;p&gt;Because this site is hosted on standard web server infrastructure:&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>We believe privacy on the web should be respected by default. This policy outlines exactly how Azathoth LLC handles data on <strong>azathothllc.com</strong>.</p>
<h2 id="the-short-version">The Short Version</h2>
<p>We do not track you, we do not profile you, and we do not sell or monetize your data. This site is completely static and private by design.</p>
<h2 id="what-we-do-not-do">What We Do Not Do</h2>
<ul>
<li><strong>No Cookies</strong>: We set zero cookies. There are no session cookies, no preference cookies, and no advertising cookies.</li>
<li><strong>No Trackers or Analytics</strong>: We do not use Google Analytics, Meta Pixel, or any client-side analytics scripts.</li>
<li><strong>No Third-Party Requests</strong>: Every asset (fonts, stylesheets, images) is served directly from our own domain. When you load a page on this site, your browser never contacts a third party.</li>
<li><strong>No JavaScript</strong>: This website runs without client-side scripts. We do not fingerprint your browser, probe your screen dimensions, or monitor your browsing behavior.</li>
</ul>
<h2 id="what-we-collect">What We Collect</h2>
<p>Because this site is hosted on standard web server infrastructure:</p>
<ul>
<li><strong>Server Access Logs</strong>: Like virtually all web servers, our hosting environment may record standard HTTP request logs (including your IP address, requested URL, user-agent string, and timestamp). These logs are used solely for infrastructure diagnostics, security monitoring, and defending against abuse.</li>
<li><strong>Direct Communication</strong>: If you choose to contact us via email at <a href="mailto:contact@azathothllc.com">contact@azathothllc.com</a>, we receive your email address and message contents to respond to your inquiry. We never add you to marketing lists or share your email with third parties.</li>
</ul>
<h2 id="inquiries">Inquiries</h2>
<p>If you have questions regarding our privacy practices or infrastructure, contact us at <a href="mailto:contact@azathothllc.com">contact@azathothllc.com</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Building Fast and Resilient Systems</title>
      <link>https://azathothllc.com/blog/building-fast-systems/</link>
      <pubDate>Tue, 17 Nov 2026 12:00:00 +0000</pubDate><author>contact@azathothllc.com (Azathoth LLC)</author>
      <guid>https://azathothllc.com/blog/building-fast-systems/</guid>
      <description>&lt;p&gt;In distributed software engineering, simplicity is the ultimate prerequisite for reliability. Complex architectures with sprawling microservice graphs often fail not from technical limitations, but from runaway operational complexity.&lt;/p&gt;&#xA;&lt;h2 id=&#34;core-architectural-pillars&#34;&gt;Core Architectural Pillars&lt;/h2&gt;&#xA;&lt;p&gt;When building systems at Azathoth LLC, we anchor every design decision on three fundamental pillars:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Minimalist Footprint&lt;/strong&gt;: Eliminate unnecessary abstractions and middle layers.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Predictable Latency&lt;/strong&gt;: Enforce bounded execution times and strict timeouts across network boundaries.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Self-Healing Topologies&lt;/strong&gt;: Ensure nodes can crash and restart safely without cascading degradation.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;step-by-step-optimization-process&#34;&gt;Step-by-Step Optimization Process&lt;/h3&gt;&#xA;&lt;p&gt;To systematically eliminate bottlenecks, follow this staged sequence:&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>In distributed software engineering, simplicity is the ultimate prerequisite for reliability. Complex architectures with sprawling microservice graphs often fail not from technical limitations, but from runaway operational complexity.</p>
<h2 id="core-architectural-pillars">Core Architectural Pillars</h2>
<p>When building systems at Azathoth LLC, we anchor every design decision on three fundamental pillars:</p>
<ul>
<li><strong>Minimalist Footprint</strong>: Eliminate unnecessary abstractions and middle layers.</li>
<li><strong>Predictable Latency</strong>: Enforce bounded execution times and strict timeouts across network boundaries.</li>
<li><strong>Self-Healing Topologies</strong>: Ensure nodes can crash and restart safely without cascading degradation.</li>
</ul>
<h3 id="step-by-step-optimization-process">Step-by-Step Optimization Process</h3>
<p>To systematically eliminate bottlenecks, follow this staged sequence:</p>
<ol>
<li>Measure baseline latency percentiles ($p50$, $p99$, $p99.9$).</li>
<li>Identify hot execution paths and unnecessary memory allocations.</li>
<li>Replace chatty RPC round-trips with pipelined or batched requests.</li>
<li>Validate under synthetic load before pushing to production.</li>
</ol>
<h2 id="system-architecture">System Architecture</h2>
<p>The diagram below illustrates the end-to-end request flow through our edge routing and worker clusters:</p>
<figure>
  <img src="/images/architecture.webp" alt="System Architecture Diagram" width="800" height="320" loading="lazy" decoding="async">
  <figcaption><p>End-to-end request flow through edge routing, microservices, and storage.</p></figcaption>
</figure>
<h2 id="efficient-worker-implementation">Efficient Worker Implementation</h2>
<p>Below is a production-ready example in Go demonstrating a bounded worker pool that handles concurrent jobs with graceful cancellation:</p>





<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="kn">package</span><span class="w"> </span><span class="nx">main</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kn">import</span><span class="w"> </span><span class="p">(</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="s">&#34;context&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="s">&#34;fmt&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="s">&#34;sync&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">worker</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="nx">context</span><span class="p">.</span><span class="nx">Context</span><span class="p">,</span><span class="w"> </span><span class="nx">id</span><span class="w"> </span><span class="kt">int</span><span class="p">,</span><span class="w"> </span><span class="nx">jobs</span><span class="w"> </span><span class="o">&lt;-</span><span class="kd">chan</span><span class="w"> </span><span class="kt">string</span><span class="p">,</span><span class="w"> </span><span class="nx">wg</span><span class="w"> </span><span class="o">*</span><span class="nx">sync</span><span class="p">.</span><span class="nx">WaitGroup</span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="k">defer</span><span class="w"> </span><span class="nx">wg</span><span class="p">.</span><span class="nf">Done</span><span class="p">()</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="k">for</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">select</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">case</span><span class="w"> </span><span class="o">&lt;-</span><span class="nx">ctx</span><span class="p">.</span><span class="nf">Done</span><span class="p">():</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="k">return</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">case</span><span class="w"> </span><span class="nx">job</span><span class="p">,</span><span class="w"> </span><span class="nx">ok</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="o">&lt;-</span><span class="nx">jobs</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="k">if</span><span class="w"> </span><span class="p">!</span><span class="nx">ok</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="k">return</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">fmt</span><span class="p">.</span><span class="nf">Printf</span><span class="p">(</span><span class="s">&#34;worker %d processed job: %s\n&#34;</span><span class="p">,</span><span class="w"> </span><span class="nx">id</span><span class="p">,</span><span class="w"> </span><span class="nx">job</span><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span></span></span></code></pre></div><h2 id="references--further-reading">References &amp; Further Reading</h2>
<p>For more details on our design philosophy, visit our <a href="/about/">About page</a> or read about the <a href="https://bearblog.dev/">Bear Blog movement</a>.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
