Containers involve a lot of complexity, sure. But a lot of that complexity is invoked in different ways with different deployment mechanisms. Using RPM to deplo

Containers involve a lot of complexity, sure. But a lot of that complexity is invoked in different ways with different deployment mechanisms. Using RPM to deploy your packages to servers? You need an update policy, curated hosts/VMs, build SPECs, etc. It's still complex as hell, just different (comfortable) complex. That said, for a lot of things, I think containers are premature optimization. People get so excited about deploying their little app that they deploy a 6 node K8S cluster with all the associated complexity, for an app that would happily run HA on two regular nodes with systemd starting it up. Once you are plumbing together a dozen different microservices using a few different languages though, K8S starts to make a lot of sense. Service discovery, container-container routing, namespacing, and all that other good stuff make your life _easier_, but only past some level of scale. Oh, and docker compose is amazing for local dev and integration testing of those more complex service compositions, just saying.