Systems | Development | Analytics | API | Testing

How to migrate AWS MSK to Express Brokers with Lenses K2K Replicator

AWS MSK has become popular because it deploys Kafka easily and bills alongside other AWS services. Over the past few years, AWS announced Express Brokers, a new cluster type that offers unlimited storage and separates brokers from storage resources. This simplifies scaling and reduces the time needed to rebalance topics when adding or removing brokers.

Lenses K2K | See the universal Kafka to Kafka replicator in action

Lenses K2K is a new Kafka to Kafka replicator that gives any user the power to easily and reliably share real-time data across their business. Why is it different to the likes of MirrorMaker2, Confluent Cluster Linking and AWS Replicator? Vendor agnostic: Replicate data to and from any cluster or vendor, from Confluent Cloud and Redpanda to AWS and Azure Event Hubs. Self service: Full self-service capabilities to empower teams to replicate data, all while governed by multi-cluster Identity and Access Management and auditing.

From hours of Kafka troubleshooting to insights in minutes

You're three hours into debugging a stalled Kafka consumer. The lag is climbing. Customers are complaining. Your logging doesn't show anything useful, and changing the log level requires a deployment approval that won't come until tomorrow morning. Sound familiar? If you're operating Apache Kafka at scale, that sinking feeling when a consumer group stops progressing, and you're left playing detective with insufficient clues.

The post-hype reality for developers

Devoxx Poland 2025 felt different. Not because of revolutionary new frameworks or another "this changes everything" moment, but because of what didn't happen. The conference had an unusual dose of pragmatism, skepticism, and – dare we say it – common sense. Maybe it's because developers are asking the right questions: "Does this solve a problem?" and "What happens when this inevitably breaks?" Here's what emerged from the sessions we watched, and the people we spoke to.

The Kafka replicator comparison guide

Let's talk about a problem that might sound simple but gets complex quickly: copying data from one Kafka cluster to another. As our Kafka usage grows, many of us find ourselves managing multiple clusters and needing to share data between them. Or worst still, sharing data to an external cluster. During a London meetup, we explored why this happens, what existing solutions offer, and why we decided to build our own Kafka replicator. Here's what we learned.

Confluent Current 2025 highlights

Current 2025 featured two days of engineers figuring out how streaming tech needs to evolve in an AI-driven world. Gone are the days when talks focused on basic Kafka setup. This year, everyone was tackling complex integrations, developer happiness, and practical AI implementation. Still, the event drew a range of people, with plenty of new faces stopping by the Lenses.io booth – clear evidence that Kafka and data streaming continue to attract newcomers.