Instead of containers, give me strong config and deploy primitives
So... systemd + Ansible?<p>I really disliked SystemD before I got my hands dirty with it. Assuming you&#x27;re developing with any modern language, the language itself probably wraps OS differences anyways (Node &#x2F; Golang &#x2F; Rust &#x2F; Ruby &#x2F; Python &#x2F; anything-libUV-based to name a few), not like you can convince developers to change their habits anyways.<p>People act like Docker makes builds reproducible by magic, then go on to not pin any Golang deps or curl internet resources or not generate lockfiles for NPM, ad infinitum.<p>There is and never will be a shield operations people can put around their developers. You just need good developers. If you want SoA scaling or automatic cloud configuration, why not just use the most established tools available? Linux&#x27;s init system and kernel _already do_ resource management, even outside of LXC. People act like a &quot;cloud scheduler&quot; is the only thing that lets multiple processes work together.<p>This whole idea of isolation is also really inane. Each app will have different disk, io, network, cpu requirements. I also dream of the day Kubernetes can do this &quot;sorting&quot; better than an experienced operations team can, but that day is _far off_ (and I will die before I put redis&#x2F;mysql&#x2F;postgres&#x2F;cassandra&#x2F;any-other-mature-datastore behind docker and iptables)