<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kafka on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/kafka/</link>
    <description>Recent content in Kafka on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 May 2022 14:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/kafka/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kafka at Startup Scale</title>
      <link>https://blog.turboawesome.win/2022/05/kafka-at-startup-scale/</link>
      <pubDate>Wed, 18 May 2022 14:00:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2022/05/kafka-at-startup-scale/</guid>
      <description>Running Kafka at a startup is different from running it at enterprise scale. The operational complexity is real, the defaults are wrong for small clusters, and the failure modes are different from what the documentation implies.</description>
    </item>
    <item>
      <title>Schema Evolution in Avro: The Hard Lessons from Production</title>
      <link>https://blog.turboawesome.win/2018/10/schema-evolution-in-avro-the-hard-lessons-from-production/</link>
      <pubDate>Thu, 04 Oct 2018 11:29:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/10/schema-evolution-in-avro-the-hard-lessons-from-production/</guid>
      <description>Avro&amp;#39;s schema evolution rules sound simple. In production with multiple services and a regulated data retention requirement, the edges are sharp. Here are the cases that burned us and the practices that prevented future ones.</description>
    </item>
    <item>
      <title>Backpressure in Practice: Keeping Fast Producers from Killing Slow Consumers</title>
      <link>https://blog.turboawesome.win/2018/06/backpressure-in-practice-keeping-fast-producers-from-killing-slow-consumers/</link>
      <pubDate>Thu, 14 Jun 2018 10:33:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2018/06/backpressure-in-practice-keeping-fast-producers-from-killing-slow-consumers/</guid>
      <description>Every system has components that produce faster than consumers can handle under some conditions. Backpressure is the mechanism by which fast producers are slowed rather than dropping data or consuming unbounded memory. Here&amp;#39;s what the options look like in practice.</description>
    </item>
    <item>
      <title>Building MiFID II Trade Reporting Infrastructure: An Engineer&#39;s View</title>
      <link>https://blog.turboawesome.win/2017/10/building-mifid-ii-trade-reporting-infrastructure-an-engineers-view/</link>
      <pubDate>Tue, 03 Oct 2017 11:45:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/10/building-mifid-ii-trade-reporting-infrastructure-an-engineers-view/</guid>
      <description>MiFID II required every trade to be reported within 15 minutes of execution. Building the infrastructure to meet that requirement across a large, heterogeneous estate taught us about the gap between regulatory requirements and production reality.</description>
    </item>
    <item>
      <title>Stream Processing with Kafka Streams vs Flink: A Real Comparison</title>
      <link>https://blog.turboawesome.win/2017/09/stream-processing-with-kafka-streams-vs-flink-a-real-comparison/</link>
      <pubDate>Wed, 27 Sep 2017 14:02:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/09/stream-processing-with-kafka-streams-vs-flink-a-real-comparison/</guid>
      <description>We evaluated Kafka Streams and Apache Flink for a real-time trade enrichment and aggregation pipeline. The technical comparison produced a clear result; the operational comparison was more nuanced.</description>
    </item>
    <item>
      <title>Kafka in Finance: What &#39;Exactly Once&#39; Actually Costs You</title>
      <link>https://blog.turboawesome.win/2017/01/kafka-in-finance-what-exactly-once-actually-costs-you/</link>
      <pubDate>Tue, 10 Jan 2017 11:22:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2017/01/kafka-in-finance-what-exactly-once-actually-costs-you/</guid>
      <description>Kafka&amp;#39;s exactly-once semantics arrived in 0.11 with significant caveats. Using it in a regulated financial context forced a clear-eyed view of what the guarantee actually covers and what it doesn&amp;#39;t.</description>
    </item>
    <item>
      <title>Chronicle Queue vs Kafka: Choosing a Persistent Journal at Nanosecond Scale</title>
      <link>https://blog.turboawesome.win/2015/01/chronicle-queue-vs-kafka-choosing-a-persistent-journal-at-nanosecond-scale/</link>
      <pubDate>Wed, 21 Jan 2015 10:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2015/01/chronicle-queue-vs-kafka-choosing-a-persistent-journal-at-nanosecond-scale/</guid>
      <description>Both Chronicle Queue and Kafka provide persistent, ordered message logs. Their performance profiles, operational models, and use cases are almost completely different.</description>
    </item>
  </channel>
</rss>
