Systems | Development | Analytics | API | Testing

Introducing K2K 2.0: Enterprise Kafka DR - without vendor lock-in

Summary Kafka has become the backbone of the real-time enterprise. The streams it carries are not only time, but business critical: a fraud event isn't processed, a sales order not fulfilled, a trade not settled. Yet we heard a recurring theme from Kafka teams: their business is running critical streaming applications without proper Kafka resiliency.

Consumer offset mapping in Kafka-to-Kafka replication

If you replicate data between two distinct Kafka clusters, you already know the payloads can match while the offsets might not. This post is about how K2K 2.0 now also keeps consumer committed offsets in sync between the source and the target so consumer groups can fail over in a Disaster Recovery situation, avoiding large re-reading of data or row skips. This offers the community more choice for DR than just MirrorMaker2 and Confluent solutions have until now.

Why Your Kafka Event Streams Need an Event Gateway

*You wouldn't expose a REST API without a gateway. What about Kafka?* You would never expose a REST API without an API gateway in front of it. Authentication, rate limiting, observability, access control — these aren't optional extras. They're mandatory, and we've spent the last decade building the API gateway pattern to solve exactly this problem. So here's the question worth sitting with: would you expose Kafka or any event stream without a gateway?

Preventing Kafka war rooms: with self-service troubleshooting

Most Kafka war rooms don't start at 2am in production. They start weeks earlier, when an engineer couldn’t explore a topic, see partition distribution, a quota or a config and shipped hoping for the best. That's the Platform Engineering waiting room: developers building apps waiting in a queue of tickets, with no self-service visibility into Kafka. That release triggers a P1 later.

Kafka in a DMZ: Protecting AWS MSK with Kong Event Gateway

Running Apache Kafka on Amazon Managed Streaming for Apache Kafka (MSK) gives you a managed broker with no ZooKeeper to operate, automated patching, and multi-AZ replication handled by the service. What it doesn't give you is a safe, governed way to expose Kafka access beyond your VPC boundary. That problem looks simple on the surface. It isn't. And how you solve it has significant implications for security posture, operational complexity, and monthly cost.

Tableflow: Turn Kafka Topics into Iceberg Tables

TL;DR: Tableflow is a Confluent Cloud feature that materializes Apache Kafka topics as Apache Iceberg or Delta Lake tables, eliminating custom data pipelines by automatically handling schematization, type conversions, schema evolution, CDC stream materialization, catalog publishing, and table maintenance.

Thousands of Migrations, Zero Data Loss: OCBC's Confluent Playbook | Life Is But A Stream

Migrating an entire bank's infrastructure without losing a single transaction sounds impossible. Yet, OCBC successfully modernized their event-driven architecture across Singapore, Malaysia, and Hong Kong with zero data loss. In this episode, George Goh (Executive Director at OCBC) joins Joseph Morais and Sami Amed (Staff Solutions Engineer at Confluent) to pull back the curtain on a massive data streaming migration, how the team executed a flawless migration of thousands of producers and consumers in a single weekend.