options for high-throughput connections between nodes

[Karl Nilsson]

You can have multiple osiris "clusters" and each one will use it's own
connection

On Fri, 1 Apr 2022 at 12:10, Dave Cottlehuber <dch@REDACTED> wrote:

> On Fri, 1 Apr 2022, at 10:48, Karl Nilsson wrote:
> > Osiris is quite a different type of thing to the other ones in your
> > list in that it will always first write terms to disk and only then
> > replicate them (over TCP). That said it could do a decent replication
> > job if you want a local buffer to decouple the production of terms from
> > the replication part. Osiris does still need a dist erl connection for
> > coordination messages and you'd have to modify the quorum commit
> > semantics to fit your use case (e.g. a "leader" member on the
> > production side and a "replica" member on the other side).
> >
> > Cheers
> > Karl
>
> Thanks Karl,
>
> Osiris is definitely worth considering - there is always the risk of
> connection loss, and need to restart from a known checkpoint, the buffer
> could come in handy. Would it be able to make use of multiple TCP
> connections?
>
> A+
> Dave
>


-- 
*Karl Nilsson*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20220401/6375e34a/attachment.htm>