DistributedLog vs Raft

[Anthony Yu]

The document says "Creating a new log segment during ownership change is known as ‘obtaining an epoch during leader election’ in distributed consensus algorithms." [1]

Did you guys have any comparison between DistributedLog and Raft[2] or any other consensus algorithms? Or did you compare with Kafka's replication [3] and its IRS (in-sync replicas)? 

We are now looking for a messaging solution to store finiancial data. It seems that DistributedLog is a good fit for us - strong consistency and durability. But we'd like to know more about its consistency model. It would be good that you guys could share your experience. And also if there are any performance numbers, that would be awesome too. (We've looked at the open source area. Kafka doesn't quite meet our requirements. performance sucks on durable writes and IRS can shrink to zero causing data loss ...)

[1] http://distributedlog.io/html/design/main.html

[2] https://raft.github.io/

[3] https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Replication

[M Rodriguez]

Hi, I'm also interested in the questions below.

Thanks for any answers!

[Sijie Guo]

(cc the apache mailing lists -  distributedlog-user@ and @distributedlog-dev@, since distributedlog is now at the ASF)

Hi Rodriguez,

I actually had a writeup about the the replication and consistency model. I will try to share it soon.

- Sijie

--
You received this message because you are subscribed to the Google Groups "distributedlog-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to distributedlog-user+unsub...@googlegroups.com.
To post to this group, send email to distributedlog-user@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/distributedlog-user/22100da2-d162-4bea-8b6f-aeb7666fe27f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.