[Cerowrt-devel] better service discovery

[dpreed at reed.com]

There's a paper from Cambridge University that focuses on evaluating Raft.  In particular they have some key findings about performance tuning, plus discovering some potential livelocks.

I'm interested in Consul on a planet-wide scale - not sure it scales effectively but if it or something like it can be made to, I have a really revolutionary use for it that I've been exploring.  So I will be playing with it - like to see if it can survive attacks in a non-friendly environment (not a datacenter) as well.

I don't know of any projects that would have experience with it in production, at least not yet.



On Tuesday, January 26, 2016 2:07am, "Aaron Wood" <woody77 at gmail.com> said:

> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> Consul is based on Raft, so anyone using Consul is using Raft.
> 
> (and we're poking around at it at my company, but I don't have any insight
> to give on it, yet).  But in general, I also like distributed redundancy
> (as opposed to primary/backup redundancy).
> 
> -Aaron
> 
> On Mon, Jan 25, 2016 at 9:40 AM, Dave Täht <dave at taht.net> wrote:
> 
>> While at last week's scale conference I ran across a guy doing
>> interesting things in tinc. One of the things he'd pointed out was the
>> general availability of service discovery options using a very flexible
>> many master/client protocol called "raft" - including using it as a dns
>> substitute in his environment.
>>
>> https://raft.github.io/
>>
>> I like things that have redundancy and distributed state. Has anyone
>> been using this in any scenario?
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel at lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>