[erlang-questions] Erlang in a WAN
Fri Mar 25 12:38:16 CET 2016
Erlang <-> Erlang I wouldn't do HTTP at all. It is just a big ball of
added serialization weight and awful type tradeoffs to boot.
term_binary/1 <-> binary_term/1 over TLS.
And that's about the whole story.
You can't do monitors and links and whatnot, so you will have to split
your architecture in a way that accommodates that.
On 2016年3月25日 金曜日 12:25:23 Sergej Jurečko wrote:
> I would not use distributed erlang for this. It is way too insecure and unsuitable for large latencies. HTTP/2 is I think the best option. Chatterbox looks quite good: https://github.com/joedevivo/chatterbox <https://github.com/joedevivo/chatterbox>
> > On 25 Mar 2016, at 12:20, Roberto Ostinelli <> wrote:
> > Forgot to mention that this is the guide I found:
> > http://erlang.org/doc/apps/ssl/ssl_distribution.html <http://erlang.org/doc/apps/ssl/ssl_distribution.html>
> > Still, war stories and opinions are warmly welcome.
> > Best,
> > r.
> > On Fri, Mar 25, 2016 at 12:17 PM, Roberto Ostinelli < <mailto:>> wrote:
> > Dear list,
> > In order to substantially reduce latencies I need to deploy some servers of an Erlang cluster in distant AWS data centres.
> > I remember reading Erlang having potential issues in WAN settings. Also, if I'm not mistaken the communication between nodes is not encrypted, which is fine if you're in the same VPC but it is not if your nodes have public IPs.
> > Does anyone have war stories / pointers on how to distribute an Erlang cluster across different AWS zones (US, EU, Asia, etc)?
> > Thank you in advance.
> > r.
> > _______________________________________________
> > erlang-questions mailing list
> > http://erlang.org/mailman/listinfo/erlang-questions
More information about the erlang-questions