0 views collected around this technical thread.
This article visually breaks down Kafka’s fundamental concepts—including producers, consumers, topics, consumer groups, partitions, and cluster architecture—explaining how messages flow, are stored, and achieve load balancing and ordering within a distributed streaming system.
This article provides a comprehensive overview of Apache Kafka, explaining its distributed message‑queue architecture, the role of topics and partitions, producer and consumer workflows, leader election, offset management, consumer‑group rebalancing, delivery semantics, transaction processing, file organization, and key configuration settings.
Kafka is a high‑performance distributed message queue that uses topics, partitions, and replicas for scalability, with producers writing messages, consumers reading them via consumer groups, and advanced features such as offset management, delivery semantics, rebalancing, and exactly‑once transactional processing, all coordinated by Zookeeper.
This article visually breaks down Kafka’s fundamental concepts—including topics, partitions, producers, consumers, consumer groups, and cluster architecture—so readers can grasp how messages flow, are stored, and achieve load balancing and ordering within a distributed streaming platform.
This article explains the fundamental concepts of Apache Kafka, including producers, consumers, topics, partitions, consumer groups, and the role of ZooKeeper in a clustered architecture, while illustrating how messages are stored, routed, and ordered for reliable, scalable stream processing.
This article explains how Kafka producers decide which partition to send messages to, how topic partition counts are configured, and how consumer groups assign partitions to instances using default range and round‑robin strategies, with code examples for illustration.
This article explains Kafka's core architecture, covering how topics and partitions are stored, the advantages of its consumption model, the internal network and threading design, and the high‑reliability distributed log storage and replication mechanisms that ensure data durability and scalability.
This article presents New Relic's 20 best‑practice recommendations for operating Apache Kafka at high throughput, covering partitions, consumers, producers, and brokers, and explains key concepts, configuration tuning, monitoring, and architectural considerations to ensure reliable, scalable streaming pipelines.
The article explains how excessive HBase partitions can cause frequent flushes, compaction storms, high memory usage, long master assignment times, and reduced MapReduce concurrency, and provides formulas and guidelines for calculating a reasonable number of regions per RegionServer.
This article explains the Unix principle that everything is a file, describes regular and special file types, outlines why and how disks are partitioned, introduces mount points, and details the standard Linux filesystem hierarchy and inode metadata.