It's all about scale. Large scale requires an orchestrated application management system with progressively integrated bells and whistles and minimal fiddling w

It's all about scale. Large scale requires an orchestrated application management system with progressively integrated bells and whistles and minimal fiddling with userspace. Small scale doesn't factor in. Do small scale the old way if you want: Binary artifacts, amis, home grown integrations and playbooks/scripts. Having done it both ways I continue to do it both ways. Run a monolith the old way and run your web tier, stateless and customer facing, highly available services in k8s. If it's not broken don't fix it (but for some use cases (large scale) the old way _was_ broken).