Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by zimbatm on Friday June 13, 2014 @05:16PM
(#7890874)
Just linking processes together is not enough to build a cluster. How do you allocate the physical resources, deal with network splits, package and deploy new code, monitor... There's a whole layer that's missing there that would surely be nice to have. The OTP framework could even be used to sandbox in LXC and start other type of applications.
[ Parent
| on HN ]
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by gordonguthrie on Friday June 13, 2014 @06:47PM
(#7891233)
Lots of that is a scoosh in Erlang, deploy, monitor, manage clusters. You have monitoring, cross-machine process linking, remote code loading all based on network transparency....
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by ghostwriter on Friday June 13, 2014 @06:33PM
(#7891172)
That is what LING (formerly erlang-on-xen) is here for: http://erlangonxen.org
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by justincormack on Saturday June 14, 2014 @05:42AM
(#7892451)
That doesnt really solve all those problems in itself does it?
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by zimbatm on Friday June 13, 2014 @06:43PM
(#7891209)
It's pretty cool but I don't think that it's open-source.
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by dragonwriter on Friday June 13, 2014 @07:05PM
(#7891300)
It seems to have an open-source, copyleft, non-GPL license [1].
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by ghostwriter on Friday June 13, 2014 @06:58PM
(#7891280)
why, you can grab the source on github: https://github.com/cloudozer/ling
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by kylequest on Friday June 13, 2014 @06:35PM
(#7891173)
Network splits and many other multi machine distributed computing problems aren't addressed well by Erlang because it was designed mostly for distributed computing within a single machine (that might have several CPUs and/or blades).
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by jacquesm on Saturday June 14, 2014 @07:25AM
(#7892575)
Erlang will work spectacularly well in those scenarios and is explicitly aimed at them, definitely not just for 'distributed computing within a single machine' (which is nonsense anyway). The reason why it can't deal well with network splits is better explained by internalizing this:
Re:Erlang/OTP – The fastest, cheapest way to build reliable ...
by klibertp on Saturday June 14, 2014 @09:26AM
(#7892720)
If I remember correctly, Erlang was designed for fault-tolerant telephone switches and there were always two of them (the switches) in one box, because the system had to cope with even hardware failures.
So Erlang is pretty much designed to deal with systems distributed on different machines, it's nice behaviour on modern multicore machines is just a byproduct of that.