Ooooh don't even go there today
. The answer is kubernetes which is not an answer but another layer of problems.
Processes are all the virtualization we really need. Containers are an excuse to let people get away with steaming shit for software architecture by pretending there is adequate isolation between the lumps of poo floating in the lake of diarrhea.
We have all the virtualization we've got because people are shit at managing shared libraries, so as soon there's more than one app per OS, their heads will fucking explode.
http://harmful.cat-v.org/software/dynamic-linking/
I'm firmly in static linking and single binary headspace.
nah, in this case the docker stuff allows for fast deployment and fan out across a multitude of backend nodes.
So once they decide to add voice recognition and real time translation I will need those back ends ...
The thing that always sits in my mind is I know there is a simpler way and I will find it ![Smiley :)](https://www.eevblog.com/forum/Smileys/default/xsmiley.gif.pagespeed.ic.R8GFI-pF6f.png)
<btdn> I never, for the life of me, understand why people like dynamic linking.
<aiju> btdn: for the very same reason they believe in god
I’ve long suspected this was true; ever since it was explained to me as part of my NetAdmin coursework exactly how a collection of .dlls works with an executable. Even with my weak Kung-Fu I could see that herding the damned things often cost more overhead than they saved, and then there’s the assache of trying to make all these generic building blocks do every specialized task we ask.
It seems to me like trying to make a sphere with only 2x4 LEGO bricks in a certain order; sure it can be done, but it’s gonna be big & lumpy no matter how you do it, and on top of that, you have to catalog every fucking brick...
![Face Palm :palm:](https://www.eevblog.com/forum/Smileys/default/xfacepalm.gif.pagespeed.ic.EBDwh1hCfo.png)
mnem
![Indifferent :=\](https://www.eevblog.com/forum/Smileys/default/indifferent0023.gif.pagespeed.ce.nyXMDasYXd.gif)