YouTube video by The ASF

An engineer's practical guide to serialization, schema evolution, and reliable event-driven systems using Java, Apache Kafka, and Schema…

What Really Happens After producer.send()?

Back in May, Tom wrote about a proof of concept for routing — Kafka clients producing and consuming from topics scattered across multiple clusters, with no idea that’s what they’re doing. The proxy ha...

Introduction

Lenses ® is a DataOps platform that provides cutting edge visibility into data streams, integrations, processing, operations and enables ethical and secure data usage for the modern data-driven enterprise.

A detailed guide to Apache Kafka covering topics, partitions, brokers, producers, consumers, replication, delivery guarantees, KRaft, and the ecosystem, with code examples and practical tips.

Apache Kafka is how most companies move event data: clicks, orders, logs, database changes. WarpStream is a newer system that speaks the…

A practical look at Kafka 4.4.0: Share Group DLQs, rack-aware partitioning, Streams state recovery, CIDR ACLs, and delayed tiered-storage uploads.

Understanding Apache Kafka’s architecture, partitions, replication, consumer groups, and the engineering principles behind reliable…

Ever added a new status to a column, or altered one, and then watched three downstream consumers fall over?

TL;DR The Apache Kafka project disclosed 12 Apache Kafka vulnerabilities. The most serious, CVE-2026-110985, lets an unauthenticated attacker forge a login token and "gain full access to the cluster." Kafka rates six of the flaws Important, three Moderate and three Low. The bugs enable authentication bypass, secret theft and memory-exhaustion crashes. Fixes ship in Kafka 4.2.2, 4.3.2 and 4.4.0. However, two fixes also need new configuration settings to fully protect brokers.

TL;DR The Apache Kafka project disclosed 12 Apache Kafka vulnerabilities. The most serious, CVE-2026-110985, lets an unauthenticated attacker forge a login token and "gain full access to the cluster." Kafka rates six of the flaws Important, three Moderate and three Low. The bugs enable authentication bypass, secret theft and memory-exhaustion crashes. Fixes ship in Kafka 4.2.2, 4.3.2 and 4.4.0. However, two fixes also need new configuration settings to fully protect brokers.

An unnecessarily deep dive into how Flink commits Kafka consumer offsets. A pull request of mine was merged into this week. A ridiculous number of sketches and diagrams went into the commits to get ...

Kafka makes it easy to distribute work across consumer instances. It is much harder to prove, safely and repeatedly, how those instances…

Retention is the clock everyone checks. It is one of several, and the rest are stored in different places, evaluated by different…

Store orders and events in one PostgreSQL transaction, publish through a polling relay, and handle repeated Kafka deliveries by event ID.

Key TakeawaysSynchronous webhook to runner systems do present some issues but we see that they are at risk for certain problems. The solution isn't to add more runners, instead what we do is we...