<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kafka on blanpa</title><link>https://blanpa.github.io/tags/kafka/</link><description>Recent content in Kafka on blanpa</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 blanpa</copyright><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blanpa.github.io/tags/kafka/index.xml" rel="self" type="application/rss+xml"/><item><title>Kafka Suite</title><link>https://blanpa.github.io/projects/kafka-suite/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://blanpa.github.io/projects/kafka-suite/</guid><description>&lt;h2 class="relative group">The Problem
 &lt;div id="the-problem" class="anchor">&lt;/div>
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem" aria-label="Anchor">#&lt;/a>
 &lt;/span>
 
&lt;/h2>
&lt;p>Apache Kafka is the de-facto standard for high-throughput event streaming in enterprise and industrial data pipelines — but getting Node-RED to talk to Kafka properly means picking a client library, wiring up Schema Registry, handling SASL/mTLS for managed services, and tuning consumer groups by hand. Existing Node-RED Kafka nodes cover the basics but fall short on schema handling, authentication variety, and production-grade connection management.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blanpa.github.io/projects/kafka-suite/thumbnail.png"/></item></channel></rss>