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 implement. However, I do n
```
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
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 diff
Hi Sohaib,
I‘m a student applying for GSOC too. And I've read all of your discussion in
the mail list.
I have some questions about your design, and some of the questions may need to
be answered by RocketMQ team. So I send them here to be discussed.
I don't think using key store to persist all