From: Aaron Wood <woody77@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] better service discovery
Date: Mon, 25 Jan 2016 23:07:23 -0800 [thread overview]
Message-ID: <CALQXh-NTnaiMGw5a2OgZj2cVcE2=YfPYDseBdkKFUStZQgy=uQ@mail.gmail.com> (raw)
In-Reply-To: <56A65E26.3040109@taht.net>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
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@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@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
next prev parent reply other threads:[~2016-01-26 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 17:40 Dave Täht
2016-01-26 7:07 ` Aaron Wood [this message]
2016-01-26 23:46 ` dpreed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-NTnaiMGw5a2OgZj2cVcE2=YfPYDseBdkKFUStZQgy=uQ@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox