Thanks a lot @ahrtr

assigning myself :)

i can't assign myself, can you please assign me ?

I would also like to participate if don't mind : )

Hi @ahrtr @Elbehery @nic-chen
Can I pick this up? I'm new to distributed systems, so this would be a good learning exercise for me.

interested in this and tend to try one if you guys has not done it

I am already working on it, thanks for your help :)

Not sure if this applies to other beginners, but I spend some time looking at the etcd server's code to understand how to wait for a proposal's commit. Thus, it would be great if we can somehow support it (probably by integrating with wait if my understanding is right.)

Can I take this over?

sorry, i am working on it :)

I expect the self-contained example should be a simple & independent example. But the PR #67 contains lots of etcd related context. Although the PR doesn't directly depend on etcd, it copies lots of etcd's source code, which may not be good.

The overall idea (using interfaces to better separate concerns) in etcd-io/etcd#15471 looks good to me, but we also need to completely remove the etcd context on top of it. @mhagger

@ahrtr If we need to implement a Raft self-contained example based on the current library, then do we only need to focus on the in-memory state, and we can without thinking about data persistence and data recovery in case of failure, such as wal and data storage ?

What's the progress of this issue?

i have a pending PR .. will continue it this week 👍🏽

thanks @peacedog123

Hi @Elbehery - is it still happening at your end ?. would be helpful to have this example for newbies in the repo.

Hello .. it is still WIP