From my point of view Erlang is an eye-opener [1]; it is a language built with the ideas - "failure happens" - "think asynchronous" - "processes, not objects

From my point of view Erlang is an eye-opener [1]; it is a language built with the ideas - "failure happens" - "think asynchronous" - "processes, not objects" and Joe had a very nice email on it [2]. K8s is "the way" but also very complex (it does not shield you from the low-level network complexity, like Erlang does). [1] https://gioorgi.com/2015/erlang-lesson1/ https://gioorgi.com/2015/erlang-lesson1/ [2] http://erlang.org/pipermail/erlang-questions/2015-April/084111.html http://erlang.org/pipermail/erlang-questions/2015-April/0841...