I have always kind of disliked both cloud and containers. Primarily, they just add more complexity and overhead into the computing landscape. I've thought this to be bad both in material resources and energy consumption, but humans have a high time preference, and therefore they choose to spend both materials and resources to get a little more time back. This is much the same reason that hipster languages and framewo…
No, they don't 'just add more complexity and overhead'. They are tools. Properly utilized, they are great.
There's a reason why you are (probably!) not running a power station and home and have, instead, hooked to a power utility company. They have the expertise and can amortize the costs among many customers.
Similarly, containers actually brought efficiency – they replaced many(obviously, not all) of the use-cases that usually required virtual machines. They also simplified some very difficult deployments.
The problem arises when you are doing things for the wrong reasons. For example, using 'microservices' just so you can try to avoid teams from having to talk to one another and end up shipping your org chart.
I do agree with a more generalized statement: more often than not, monoliths are what you need.