Systems | Development | Analytics | API | Testing

First in a 3-part series on self-service K2K replication. This post tackles how to give self-service access to deploy K2K without handing over the keys to your Kafka clusters. Lenses developed K2K (Kafka-to-Kafka) to solve two major problems: This includes making it as self-service as possible so developers can deploy without requiring a PhD in MirrorMaker2. One key design requirement: don’t force engineers to manage credentials to authenticate with Kafka.

In 2025, Model Context Protocol (MCP) captured the imagination of the AI engineering community. 2026 will be the year that everyone realises their prototypes need to run in production.

Queues for Kafka is now in General Availability (GA) on Confluent Cloud and is coming soon to Confluent Platform, coinciding with the Apache Kafka 4.2 release. This milestone brings production-ready queue semantics and elastic consumer scaling natively to Kafka through KIP-932, enabling organizations to consolidate their messaging infrastructures while gaining elastic consumer scaling and per-message processing controls. Get started.