
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Sat, 08 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/consumer-groups/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/3-kafka-mechanics</guid>
    <title>Scaling the API: Kafka Mechanics That Matter for Scale</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/3-kafka-mechanics</link>
    <description>Just enough Kafka to reason about scale, not a tutorial. Partitions are the unit of parallelism, keys decide ordering, consumer groups divide the work, and partition count bounds throughput. Then the delivery semantics that shape everything downstream: at-least-once versus exactly-once, and what each really costs.</description>
    <pubDate>Sat, 08 Aug 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>api-backend</category><category>kafka</category><category>partitions</category><category>consumer-groups</category><category>delivery-semantics</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
