<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Event Driven Architecture - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Event Driven Architecture Articles feed</description>
    <item>
      <title>Article: Building a Session-Ordered Kafka Pipeline in Go</title>
      <link>https://www.infoq.com/articles/apache-kafka-golang-session-ordered-pipeline/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Event+Driven+Architecture-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/apache-kafka-golang-session-ordered-pipeline/en/headerimage/apache-kafka-golang-session-ordered-pipeline-header-1790945957360.jpg"/&gt;&lt;p&gt;The article describes a custom implementation that provides a session-level ordering on top of Apache Kafka partitions, supporting strict message ordering across 1000s of independent channels. The solution required application-level routing, consistent hashing, retries, and contiguous watermark commits. Engineers conducted operational hardening supported by extensive performance testing.&lt;/p&gt; &lt;i&gt;By Joshua Oluikpe&lt;/i&gt;</description>
      <category>Event Stream Processing</category>
      <category>Apache Kafka</category>
      <category>Redis</category>
      <category>Event Driven Architecture</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 07 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/apache-kafka-golang-session-ordered-pipeline/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Event+Driven+Architecture-articles</guid>
      <dc:creator>Joshua Oluikpe</dc:creator>
      <dc:date>2026-10-07T09:00:00Z</dc:date>
      <dc:identifier>/articles/apache-kafka-golang-session-ordered-pipeline/en</dc:identifier>
    </item>
  </channel>
</rss>
