|
There are several layers of abstraction here, all bringing benefits. Layer 1: bare metal servers, bare metal routers, hardware appliances, etc. Layer 2: virtual servers, VLANs/security groups/etc, some appliances. Layer 3: containers, container networks, storage resources, etc. Kubernetes, arguably Heroku. Layer 4: functions as a service? In the article the suggestion, or how I read it, is essentially "Kubernetes is nothing new, we've had [layer 2] for years". However I see Kubernetes as sitting squarely in "layer 3" here. These layers are pretty subjective, all of the boundaries are blurred, but when I'm working these do require fairly different skills sets. I've never had the skillset to work at "1", I was fairly good at "2" for a while, but spent too much of my time working on that and too little shipping software, so my workplace moved to Kubernetes and it allowed me as an application engineer to do much less infra work, and for it to be at "3" when necessary. To just write off everything in "3" as being "virtualisation" is ignoring the significant step in level of abstractions and the benefits brought by that. |