Systems | Development | Analytics | API | Testing

How Multi-Kafka impacts data replication strategy

Imagine an airline system monitoring traffic around an airport. If it detects a major delay, countless systems may need to react instantly: Ground operations to adjust flows. Some of these systems will still connect via API, traditional MQ or iPaaS technologies, but the data’s volume and urgency and the ease of decoupling apps make architecting with Kafka the better fit. The natural question is: should all these applications & systems connect to the same Kafka cluster?

The True Cost of Kafka Replication

Kafka cluster-to-cluster data replication is critical to many use cases: disaster recovery (DR), cloud or data center migration, testing applications with production-like data, and multi-region data distribution. Easy replication of data between clusters: The business case is clear, but the cost model is not. Some solutions appear free but impose heavy operational burden.

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.