Be careful with analogies
I love to read TP Morgan. To my understanding, here he is advocating one approach in a debate, so is naturally a bit biased.
It is true that the time has come to have many new applications running in containers, orchestrated by Kubernetes or ECS (AWS specific flavor of container orchestration). It is also true that simple analogy with how virtualization entered enterprise computing (it was embedded on mainframes for decades) and workloads moved from physical to VMs does not hold for transition to containers. I successfully virtualized many applications without a single code change, usually even without any support from their developers. Can you do that way moving into containers? (Hint: 9 out of 10 times, no. Out of these 9, 7 can run in container, but you will be sorry you did it as it brings more problems than benefits and support and troubleshooting becomes harder). We all know that business application is a king. There are still COBOL applications running. It is unrealistic to expect that all J2EE, .NET etc based application made in last two decades will be reengineered only to fit into containers.
The sweet spot for containers are stateless workloads where one may need rapid scaling up or down (in matter of seconds). That is usually what very large and Internet companies need. SMEs, not so much. For stateful applications they bring challenges, one of which is more variable latency in I/O.
It will be interesting in next few days to read articles written from different view points.