<?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>System-Design on HFT Engineer's Roadmap</title><link>https://hftengineer.com/tags/system-design/</link><description>Recent content in System-Design on HFT Engineer's Roadmap</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hftengineer.com/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>The single-writer principle</title><link>https://hftengineer.com/posts/single-writer-principle/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://hftengineer.com/posts/single-writer-principle/</guid><description>A short walk through the single-writer principle: why exactly one thread should mutate a piece of state, why this is faster than &amp;lsquo;real&amp;rsquo; lock-free code in most cases, and how the Disruptor pattern operationalises it.</description></item></channel></rss>