I'm highly interested in this feature. We are a startup right now so we can't commit resources to help *yet*, but once we are off the ground in 1-2 years it would be cool to contribute to this.
Colt McNealy *Founder, LittleHorse.dev* On Fri, May 19, 2023 at 10:14 AM hzh0425 <hzh0...@apache.org> wrote: > Hi, Grep Harris. > When I saw this discussion, I was very excited. > My team is a Kafka R&D team, currently planning research and development > on cluster linking. We believe that it is of great value in scenarios such > as multi region disaster recovery and cross cloud synchronization. > Therefore, I hope to join the subsequent design and development of this > KIP as a co-author for deep participation. > > Thanks! > hzh > > > > > > ---- 回复的原邮件 ---- > | 发件人 | Greg Harris<greg.har...@aiven.io.INVALID> | > | 日期 | 2023年05月20日 00:56 | > | 收件人 | dev@kafka.apache.org<dev@kafka.apache.org> | > | 抄送至 | | > | 主题 | [DISCUSS] Cluster Linking / Cross-Cluster Replication - Call for > Interest & Co-Authors | > Hey all, > > I have heard some offline discussion around Cross-Cluster Replication, > a feature which would enable data to be shared between Kafka clusters > in a manner which preserves offsets. > Other names for this feature may include "Cluster Linking", "Remote > Topics", "Byte-for-Byte Mirroring", and similar. > I believe that there may be an interest in this feature being added to > Apache Kafka, but have not seen any mailing list activity to that > effect yet. > > Due to the complexity of the feature, I think it is appropriate to > gauge the interest in the feature before opening a KIP, and also > gather a set of contributors which are interested in collaborating on > and sponsoring its development. > > If you are a Kafka user, please: > 1. Let us know in this thread if you think Cross-Cluster Replication > is a valuable feature and would like to see it in Apache Kafka. > > If you are or want to be an individual contributor, please: > 1. Discuss with your users and/or product organization if > Cross-Cluster Replication is appealing, and summarize their level of > interest in the below thread. > 2. Consider volunteering in this thread as a reviewer or co-author of > the KIP and subsequent implementation. Co-authors would share the > design and implementation workload as their time and interest permits. > 3. If you have an employer, request that they sponsor this feature > through your full- or part-time contributions as a reviewer or > co-author. In exchange for their sponsorship, they can help ensure > that the feature is delivered with a more predictable timeline. > > Please save your technical expectations and details of this feature > for a subsequent KIP and DISCUSS thread, where that discussion is more > appropriate. > > Thanks Everyone! > > Greg Harris > Aiven, Inc >
