I'm not too young and I saw various methods of deploying code in production: deb packages, tarballs, docker images, static binaires. I have to say that in my e

I'm not too young and I saw various methods of deploying code in production: deb packages, tarballs, docker images, static binaires. I have to say that in my experience for a specific use case of a highload c++ daemon, nothing beats the simplicity and reliability of the static binary with musl. You only want to deploy one thing, you have nothing to share, furthermore you wouldn't want to share anything for the sake of control. So many things to worry about and to waste time on just disappear. When things are on fire having less variables to check is gold.