<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>21 nov. 2015 kl. 21:52 skrev Felix Gallo <<a href="mailto:felixgallo@gmail.com">felixgallo@gmail.com</a>>:<br><br></div><blockquote type="cite"><div><div dir="ltr">Erlang is already like a miniaturized operating system implementing well-scheduled lightweight microservices, and releases (<a href="http://www.erlang.org/doc/design_principles/release_structure.html">http://www.erlang.org/doc/design_principles/release_structure.html</a>) are already a redistributable, self-contained, minimizable unit of deployment that can be monitored, inspected and logged using standard unix workflow.<div><br></div><div>In my opinion, the cost-benefit of using docker is highly questionable even in its optimal use case, where the dev team is composed entirely of inexperienced front end javascript developers trying to deploy monolithic microservices and pretending they're being lightweight. Maybe there's a case to be made for tooling which takes languages with terrible manageability and hides them behind something, but it's not at all clear that docker is the answer to that or any other question. It makes a negative amount of sense to layer the highly ceremonial, unperformant, problem-multiplying docker abstraction on top of an actually light, already existing microservices architecture, and I wouldn't wish ownership of the resulting mutant chimera on my worst enemy. But again -- my personal opinion.</div><div><br></div><div>F.</div></div></div></blockquote><div><br></div><div>Perhaps this is true for homogeneous systems such as systems only built with Erlang components. Many systems are however hybrid systems with different component types and a container architecture (such as docker) could help in making things more homogeneous.</div><div><br></div><div>Stefan</div><div><br></div><div><br></div><div><br></div><br><blockquote type="cite"><div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 21, 2015 at 11:04 AM, Kevin Montuori <span dir="ltr"><<a href="mailto:montuori@gmail.com" target="_blank">montuori@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>>>>> "dg" == David Goehrig <<a href="mailto:dave@nexttolast.com">dave@nexttolast.com</a>> writes:<br>
<br>
dg> At work, we've been deploying a wide range of Erlang apps on<br>
dg> Docker. I'm working on a blog post ( and presentation ) on how<br>
dg> we manage our containers across multiple cloud providers.<br>
<br>
Hi David --<br>
<br>
I realize this is digging up a post from nearly six months ago but I'm<br>
wondering if this blog post materialized? Or if anyone out there had<br>
new thoughts on distributed Erlang and Docker?<br>
<br>
Thanks!<br>
<span class="HOEnZb"><font color="#888888">k.<br>
<br>
<br>
--<br>
Kevin Montuori<br>
<a href="mailto:montuori@gmail.com">montuori@gmail.com</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>erlang-questions mailing list</span><br><span><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a></span><br><span><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a></span><br></div></blockquote></body></html>