many thanks! :) Il giorno domenica 15 maggio 2016 14:24:42 UTC+2, Bram Verburg ha scritto: > > There is little point in connecting nodes just for the sake for connecting > them. If each node can do its job in isolation, and you don't need a shared > cache or something like that, just leave it as is. > > Bram > > > On Saturday, 14 May 2016 20:39:05 UTC+3, Matteo Giachino wrote: >> >> I have an elixir application on two nodes. This is mainly for >> availability, so we are doing rolling deploys on them. >> Now, I'm just coming back from elixir conference in berlin, and many >> talks were about scaling erlang beams on many nodes and the likes. >> >> Our current setup is: >> >> the app is containerized with docker and deployed on ecs. Its only >> purpose is to respond to api calls. There is a load balancer in front that >> route the requests in a round robin fashion on the two containers. So the >> two nodes are not aware of each other and behave like a single node >> application. >> >> Is there some drawbacks by doing this? Is there something that I'm >> missing from the awesome erlang virtual machine? Should I join the two >> containers togheter? >> >> Many thanks in advance. >> >
-- You received this message because you are subscribed to the Google Groups "elixir-lang-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-talk/40fe376b-1281-4d29-888c-80cc9a66a711%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
