+1 for renaming. > If we now rename MultiLeaderConsensus to IoTConsensus, what should we call it > in the future when we finds a better tradeoff between consistency and > performance?
maybe finally we will have a IoT consensus protocol family... Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 谭新宇 <[email protected]> 于2022年11月26日周六 17:21写道： > > Hi， > > For these two reasons, I strongly agree with the name change. > > Users do not need to know the name of MultiLeader which is strongly related > to the implementation. However, as the consensus module is currently an > extensible framework, more consensus algorithms may be integrated in the > future. At present, RatisConsensus is the consensus algorithm with the > strongest consistency and the worst performance, while MultiLeaderConsensus > is the consensus algorithm with the weakest consistency and the strongest > performance. There may be some new tradeoff between consistency and > performance in the future. > > If we now rename MultiLeaderConsensus to IoTConsensus, what should we call it > in the future when we finds a better tradeoff between consistency and > performance? > > Thanks > ——————————— > Xinyu Tan > > > 2022年11月26日 11:20，Jialin Qiao <[email protected]> 写道： > > > > Hi, > > > > We plan to rename MultiLeaderConsensus to IoTConsensus > > > > 1. MultiLeader does not have many degrees of identification, and IoT > > is our characteristic. > > 2. The abbreviation of MultiLeader is ML, which is conflict with > > Machine Learning, which we may introduce in IoTDB in the future. > > > > Thanks, > > ————————————————— > > Jialin Qiao > > Apache IoTDB PMC >
