Introducing Cluster Linking in Confluent Platform 6.0

Confluent has released Cluster Linking, a new concept that defines a communications link between two independent Apache Kafka clusters and introduces a new way to manage "mirrored" topics that traverse clusters. This feature enhances the Kafka architecture by advancing data protection and sharing capabilities. It allows for seamless topic mobility, cloud-bursting, and effective disaster recovery scenarios. With Cluster Linking, topics can be mirrored across clusters with zero external components or services required, replicating data partition for partition, byte for byte, as well as important metadata. The mirror topic will naturally offset-preserving and (almost) logically identical to its source topic once caught up from a client's perspective. Mirror topic replication is real-time and continuous, performed asynchronously to minimize the impact on its source topic. Cluster Linking unlocks various use cases, including seamless migration of topics across clusters, cloud-bursting, and disaster recovery scenarios. It makes topic mobility easy by allowing clients to move to new clusters without data reconciliation necessary. Looking forward, Cluster Linking will better support hybrid cloud scenarios, enabling a repeatable, secure, and reliable data highway for hybrid cloud apps, temporary cloud bursts, or low-downtime and no-data-loss cloud migrations.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.