Kafka replication meant choosing between cloud providers and clunky operations. Until now.
Current replication solutions force impossible trade-offs between vendor lock-in and operational complexity. The fundamental problems:
There's little choice. Time for a solution that works across any platform, while being both powerful and simple to use.
A new Kafka replicator that gives any user the power to easily and reliably share real-time data across their business.
To avoid vendor lock-in and replicate data across any cluster and vendor, from Confluent Cloud and Redpanda to MSK and Azure Event Hubs.
Full self-service capabilities to empower teams to replicate data, all while governed by multi-cluster Identity and Access Management and auditing.
Built by the elite engineering team behind the Lenses SQL engines.
Blog
The state of Kafka replication
By
Andrew Stevenson
Case study
Blog
The Kafka replicator comparison guide
By
Adamos Loizou
Docs
Docs
Docs
Companies replicate Kafka clusters for several reasons: disaster recovery and business continuity, data sharing between teams or external partners, vendor migration to avoid lock-in, workload migration between environments (on-prem to cloud), and data subsetting for testing with production-like data.
Read more >Kafka replication typically works by consuming messages from source topics and producing them to destination topics, often with additional features like schema registry synchronization, consumer offset translation, and topic configuration replication.
Read more >MirrorMaker 2 (MM2) is the open-source standard but requires complex Kafka Connect setup and lacks modern features. Commercial alternatives like Confluent Replicator offer support but inherit MM2's complexity. Cloud-native solutions like AWS MSK Replicator are easier but vendor-specific.
Read more >For K2K, yes. But not all other solutions do. While some tools like MirrorMaker 2 and Confluent Cluster Linking support exactly-once semantics, others like Confluent Replicator and AWS MSK Replicator do not, potentially leading to duplicate messages.
Read more >Lenses K2K automatically handles schema registry synchronization between clusters, including different schema registry types. It manages schema evolution and compatibility checks, supporting Avro, Protobuf, and JSON schemas.
Read more >Lenses K2K is a java-based application designed to run on Kubernetes, ideally close to the target Kafka cluster that you are replicating to.
The Lenses Developer Experience will help you identify the correct Kubernetes cluster to deploy to, and do all the deployment.
Read more >There is a free version that's restricted and accessible to download. A restricted version will also be included in Lenses Community Edition. For all enterprise features, you need to be a subscribed Lenses customer. Contact our teams for more information on pricing.
Request quote >K2K is available as a standalone container. But you will be responsible for the deployment, governance, and monitoring. We recommend the simplicity and power of managing K2K through the Lenses Developer Experience, found in Lenses 6.