Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Yukon, What do you suggest for the key store itself? Do you propose writing this ourselves or using some existing solution and writing a layer on top? Thanks, Sohaib On Fri, Mar 9, 2018 at 6:20 AM, yukon wrote: > ``` > Personally, I find RAFT to be much simpler to

Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

``` Personally, I find RAFT to be much simpler to implement. However, I do not expect to reinvent the wheel here. ``` That's absolutely right, no need to reinvent the wheel, there are many existing implementations for raft: https://raft.github.io/ ``` I don't think using key store to persist all

Re: 答复: [GSOC|ROCKETMQ-124] Support non-redundant message delivery mechanism

Hi Dexin, Thank you for your suggestions. I will try to answer as much as I can and leave the rest to the RocketMQ team. 1. The idea with incremental Ids is actually quite good. But @Yukon mentioned that duplication can also be controlled by an application (special KV Property) in which case