<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Felix blog: durability</title>
    <link>https://getfelix.dev/topics/durability/</link>
    <description>Felix blog posts about durability.</description>
    <language>en</language>
    <atom:link href="https://getfelix.dev/topics/durability/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Five weeks, 562 commits: Felix from 0.5.0 to 0.6.0</title>
      <link>https://getfelix.dev/blog/felix-0-5-to-0-6.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/felix-0-5-to-0-6.html</guid>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <description>What we found, fixed and added between Felix 0.5.0 and 0.6.0: the bugs that shared one shape, the ways we found them, the features that apps asked for and why, and what building it taught us.</description>
    </item>
    <item>
      <title>Fast, without losing messages</title>
      <link>https://getfelix.dev/blog/fast-without-losing-messages.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/fast-without-losing-messages.html</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <description>How Felix answers a fsynced publish in a third of a millisecond, writes at the disk&#39;s full rate under load, and slows publishers down instead of dropping their messages.</description>
    </item>
    <item>
      <title>Acknowledged, then forgotten: a crash under periodic fsync</title>
      <link>https://getfelix.dev/blog/acknowledged-then-forgotten.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/acknowledged-then-forgotten.html</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <description>Under Felix&#39;s default periodic fsync, a crashed broker could come back missing records it had acknowledged while the cluster still counted it as caught up; this is how review and the TLA+ model found it on the follower and leader sides, and what the fix costs.</description>
    </item>
    <item>
      <title>The follower that forgot</title>
      <link>https://getfelix.dev/blog/the-follower-that-forgot.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/the-follower-that-forgot.html</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <description>On an idle shard nothing ships, so a leader never learned that a follower had lost its disk; this is how a storage identity per data directory fixed that, and why it changes only when a directory may hold less than its peers were told.</description>
    </item>
    <item>
      <title>Introducing Felix: one log for streams, caches and counters</title>
      <link>https://getfelix.dev/blog/introducing-felix.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/introducing-felix.html</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
      <description>What Felix is, how a publish travels from a client to disk to every subscriber, why it is built that way, and how to run it on your laptop in five minutes.</description>
    </item>
  </channel>
</rss>
