<?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 cloudmato.com</title><link>https://cloudmato.com/tags/kafka/</link><description>Recent content in Kafka on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Wed, 03 Jun 2026 11:55:22 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/kafka/index.xml" rel="self" type="application/rss+xml"/><item><title>How Kafka Manages a Cluster and Routes Consumers Right</title><link>https://cloudmato.com/posts/kafka-cluster-management-consumer-routing/</link><pubDate>Wed, 03 Jun 2026 11:55:22 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/kafka-cluster-management-consumer-routing/</guid><description>&lt;p&gt;Kafka looks deceptively simple from the outside — you publish to a topic, someone reads from it. Under the hood it is a fairly intricate distributed system where several pieces have to agree on who owns what before a single byte gets delivered. I spent a good amount of time untangling this, and most articles stop at &amp;ldquo;partitions give you parallelism&amp;rdquo; without explaining the actual handshake. Let me go deeper.&lt;/p&gt;</description></item></channel></rss>