https://ryanorban.com/categories/apache-kafka/Recent content in Apache-Kafka on Ryan OrbanHugoen-usme@ryanorban.com (Ryan Orban)me@ryanorban.com (Ryan Orban)Ryan OrbanWed, 24 Jul 2013 00:00:00 +0000https://ryanorban.com/notes/apache-kafka-introduction/Wed, 24 Jul 2013 00:00:00 +0000me@ryanorban.com (Ryan Orban)https://ryanorban.com/notes/apache-kafka-introduction/<p><img src="https://ryanorban.com/images/notes/apache-kafka-introduction.png" alt="Introduction to Apache Kafka (TriHUG, July 2013)" class="note-hero-img" loading="lazy" /> </p> <h3 id="summary" class="scroll-mt-8 group"> Summary <a href="#summary" class="no-underline hidden opacity-50 hover:opacity-100 !text-inherit group-hover:inline-block" aria-hidden="true" title="Link to this heading" tabindex="-1"> <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" class="lucide lucide-link w-4 h-4 block" viewBox="0 0 24 24" > <path d="M10 13a5 5 0 0 0 7.54.54l3-3a5 5 0 0 0-7.07-7.07l-1.72 1.71" /> <path d="M14 11a5 5 0 0 0-7.54-.54l-3 3a5 5 0 0 0 7.07 7.07l1.71-1.71" /> </svg> </a> </h3> <p>This Triangle Hadoop User Group (TriHUG) talk from July 2013 introduced Apache Kafka to a Hadoop-focused audience at a moment when Kafka was still a relatively unknown tool. LinkedIn had built Kafka to solve a specific problem: moving high-volume activity data (page views, clicks, searches) between their production systems and their analytics Hadoop cluster without data loss or coupling. The open-source release in 2011 had given the Hadoop community access to a distributed, durable, high-throughput message queue with fundamentally different semantics than existing messaging systems.</p>