<?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 Rik Kisnah - Blog</title><link>https://www.rik-kisnah.ai/tags/kafka/</link><description>Recent content in Kafka on Rik Kisnah - Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 19 May 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://www.rik-kisnah.ai/tags/kafka/feed.xml" rel="self" type="application/rss+xml"/><item><title>Design a Telemetry Platform</title><link>https://www.rik-kisnah.ai/teach/systems/design-a-telemetry-platform/</link><pubDate>Tue, 19 May 2026 09:00:00 -0700</pubDate><guid>https://www.rik-kisnah.ai/teach/systems/design-a-telemetry-platform/</guid><description>Ingest, process and serve large-scale telemetry to stakeholders with different needs and different sensitivities. Then the follow-up: clients you cannot upgrade emit five names for the same metric. Design the pipeline, then the alias registry that fixes names without ever merging the wrong two.</description></item><item><title>Design a One-to-One Chat</title><link>https://www.rik-kisnah.ai/teach/systems/design-a-one-to-one-chat/</link><pubDate>Tue, 21 Apr 2026 09:00:00 -0700</pubDate><guid>https://www.rik-kisnah.ai/teach/systems/design-a-one-to-one-chat/</guid><description>One-to-one, text only, web only. That is all the interviewer gives you. Ask for the rest, then design the gateway that finds the recipient, the inbox that survives them being offline, the presence key that expires on its own, and defend Redis Pub/Sub against Kafka out loud.</description></item></channel></rss>