http://localhost:1313/categories/architecture/Recent content in Architecture on LorbicHugoenThu, 02 Apr 2026 12:00:00 +0530http://localhost:1313/10-years-of-lorbic.com-architecture/Thu, 02 Apr 2026 12:00:00 +0530http://localhost:1313/10-years-of-lorbic.com-architecture/<p><picture class="optimized-image-container"><source srcset="http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_c3df73cc291f2d3a.webp 480w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_d6eb9db6213c4dc9.webp 800w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_156b083258cf7313.webp 1200w, http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_abf66fd5579991cd.webp 3068w" sizes="(max-width: 800px) 100vw, 800px" type="image/webp"><img src="http://localhost:1313/10-years-of-lorbic.com-architecture/evolution_hu_abf66fd5579991cd.webp" width="3068" height="800" alt="Lorbic Evolution: 2017 vs 2026" loading="eager" decoding="async" fetchpriority="high" class="img-fluid" /> </picture></p> <p>This post tracks four architectural rewrites of my personal site over ten years: moving from managed platforms (Blogger) to dynamic backends (Django), static site generators (Jekyll/Hugo), and finally to a custom, zero-dependency architecture built for absolute control and performance.</p> <hr> <h2 id="technical-context">Technical Context<a class="anchorjs-link" href="#technical-context" aria-label="Link to section: Technical Context"></a></h2><p>For an engineer, a personal site is the only project where you have absolute authority over the stack. There are no product managers, no legacy constraints, and no enterprise technical debt: you own the metal.</p>http://localhost:1313/building-production-ready-background-workers-in-python/Sun, 01 Feb 2026 13:00:00 +0530http://localhost:1313/building-production-ready-background-workers-in-python/<p>I thought processing audio in the background was simple: spawn a thread, run the script, save the file. Then I hit 200 concurrent requests, and it failed epically.</p> <p>The CPU spiked to full usage because of pydub&rsquo;s processing. The TTS API didn&rsquo;t rate-limit me but, it was horribly slow. Then the jobs started failing. Half the jobs died silently. The other half wrote corrupted files because of race conditions I didn&rsquo;t know existed. And when I deployed a little fix? The deployment killed in-flight jobs, leaving orphaned audio segments scattered across cloud storage directory.</p>