Install

Learn how to install Lenses Kafka to Kafka Replicator

Found an issue? Feed it back to us at Github, on Slack, Ask Marios or email.

Deployment Recommendation

For optimal performance, minimal latency, and the highest degree of operational reliability, it is imperative that K2K replicator instances are deployed within the same infrastructure as the target Kafka-compatible API solution.

This co-location strategy is not merely a suggestion; it's a fundamental best practice that directly addresses the architectural and performance characteristics of Kafka:

• Mitigating Producer Latency: Kafka producer operations (which K2K heavily relies on for writing to the target) are extremely sensitive to network latency. Placing K2K instances geographically close to the target cluster drastically reduces network round-trip times for these critical writes.

• Preventing Timeouts and Retries: Shorter network paths directly translate to a lower probability of TimeoutException errors and subsequent retries, which can otherwise introduce significant delays and resource overhead.

• Maximizing Throughput & Stability: Reduced latency and fewer retries collectively lead to significantly improved overall replication throughput and enhanced system stability, ensuring data flows smoothly and consistently.

• Enabling Robust Delivery Guarantees: Proximity to the target cluster inherently strengthens K2K's ability to maintain and enforce robust delivery guarantees, including the vital exactly-once semantics, by ensuring timely and reliable communication for state management.