the problem is not the division of a monolith into microservices but the over-engineering of those microservices. No you dont need docker. My recent .net core

the problem is not the division of a monolith into microservices but the over-engineering of those microservices. No you dont need docker. My recent .net core project had 3 projects (FE - API - Dashboard). Each one was deployed with CI to their respective server but deployment, qa etc was done all outside of a docker env because there was nothing the env can alter. We knew we develop in windows 10 and deploy/qa in ubuntu xenial. the CI was configured around that and then send the dlls to the server and restart apache after deployment. The only thing that I can see for the need of docker is if you want to include your database inside also, but we opted-in for an on cloud db (azure) and each service had its own. Once again we go to the discussion in which the problem is not the technique (microservices) but the over-engineering of such solutions.