<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Felix blog: compatibility</title>
    <link>https://getfelix.dev/topics/compatibility/</link>
    <description>Felix blog posts about compatibility.</description>
    <language>en</language>
    <atom:link href="https://getfelix.dev/topics/compatibility/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The data came back</title>
      <link>https://getfelix.dev/blog/the-data-came-back.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/the-data-came-back.html</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate>
      <description>Deleting a Felix stream or cache and creating one with the same name could bring back the old one&#39;s data; this is how incarnations fixed it, and how we kept control-plane members on different releases from storing different answers during the rollout.</description>
    </item>
    <item>
      <title>Point your Kafka client at Felix</title>
      <link>https://getfelix.dev/blog/point-your-kafka-client-at-felix.html</link>
      <guid isPermaLink="true">https://getfelix.dev/blog/point-your-kafka-client-at-felix.html</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate>
      <description>Felix brokers speak enough of the Kafka wire protocol for Kafka producers and partition-assigning consumers to use durable Felix streams; this is how a Kafka request becomes a Felix operation, how idempotent sequences survive a failover, and exactly where compatibility stops.</description>
    </item>
  </channel>
</rss>
