My assessment is that if you have a large, complex micro service environment with several applications, docker may be a good route to take as an interim to clou

My assessment is that if you have a large, complex micro service environment with several applications, docker may be a good route to take as an interim to cloud native. If you have a relatively simple deployment structure (one big application with 10-20 services), maybe you don't need to add the docker skill to what you're already doing. If you're in the process of rebuilding your applications and you've decided cloud native is the way to go, then containers are pointless. I'd argue if you don't have the skills and you don't want to pay someone to do this work full-time, you might put your developers in a position to fail. Based on my 30+ years of building software, I see containers as a dead end. It may help you out in the short term, prove to your CTO that you're using "well-known" technology, but in the end, cloud native is going to replace everything. And before you say "but we can't be in the cloud," then you should know that cloud-native development like Lambdas can be done on-prem as well. I'm positive this post will get negative votes. That's fine. I like tilting at windmills.