<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backend on On the Way to Another Dawn</title>
    <link>https://lukastymo.com/tags/backend/</link>
    <description>Recent content in Backend on On the Way to Another Dawn</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 16 Apr 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://lukastymo.com/tags/backend/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stateful Kafka Streams Processors: Reducing Rebalancing - Lessons Learned</title>
      <link>https://lukastymo.com/posts/028-stateful-kafka-stream-processors/</link>
      <pubDate>Thu, 16 Apr 2026 12:00:00 +0000</pubDate>
      <guid>https://lukastymo.com/posts/028-stateful-kafka-stream-processors/</guid>
      <description>&lt;h1 id=&#34;stateful-kafka-streams-processors-reducing-rebalancing---lessons-learned&#34;&gt;Stateful Kafka Streams Processors: Reducing Rebalancing - Lessons Learned&lt;/h1&gt;&#xA;&lt;p&gt;Stateful Kafka Streams on Kubernetes need configuration to stay stable during rolling updates without causing lag. If your processor must be fast, runs on few partitions, and short lag matters, the defaults are not enough. Enable static membership with a timeout based on the worst-case duration of your rolling updates.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
