[erlang-questions] Erlang in a WAN

[Sergej Jurečko]

Any kind of way you slice it you're doing serialization. Either Erlang's RPC does term_to_binary or you do it. Makes very little difference. At least with HTTP/2 or something similar, you can carefully manage what gets called. Personally I would be very worried about exposing the capability of calling any erlang function in my application from across the world.
HTTP/2 or Thrift would honestly be my only choices. HTTP/2 is easier. 


> On 25 Mar 2016, at 12:40, Roberto Ostinelli <roberto@REDACTED> wrote:
> 
> HTTP/2? That is rather surprising. Why would that be a best option?
> 
> For instance, this would mean that a message going from a node in the EU to a node in the US would need to be serialized into an HTTP/2 request?