I think the typical experienced Erlang user would keep the C/C++ programs, but manage them through a fabric of Erlang code. That is, each part is cut up into a

I think the typical experienced Erlang user would keep the C/C++ programs, but manage them through a fabric of Erlang code. That is, each part is cut up into a small program, and these are controlled by the Erlang system so it acts like a supervisor of the programs. They are run under some kind of "visor" so their resources are limited to sane values etc. When the C/C++ program does something bad, the Erlang system is notified of this. It can then take action in order to keep the processing pipeline running. You could argue that in the current context of containers, this is easy to achieve with them. But I claim writing all of this in a programming language is far more manageable than trying to handle the rate at which the whole container-context is evolving.