Monolith are NOT simple to scale. The fact that you can run them in a scaling architecture doesn't mean it's easy. It's actually hard due to several reasons:
it's very difficult to reliably measure real espurce consumption. You can deploy them on dedicated vms with dedicated resources in the way of 1 Monolith =1 VM and add more as needed but it's neither fast nor efficient to do so ( some resource waste is unavoidable, on the fly provisioning can't match up peak demand or address spikes)
single code bases can become very large depending on application type which also affects the ability to deploy
They are NOT easy to develop.
You need to sync work from many people on the same code base to orchestrate a deploy. Whereas for a microservice you can do targeted changes and deploy fast, monoliths need a lot of preemptive integration work before deploys (microservice need that continuously but it doesn't affect the act of deploying)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Monolith are NOT simple to scale. The fact that you can run them in a scaling architecture doesn't mean it's easy. It's actually hard due to several reasons:
They are NOT easy to develop.
You need to sync work from many people on the same code base to orchestrate a deploy. Whereas for a microservice you can do targeted changes and deploy fast, monoliths need a lot of preemptive integration work before deploys (microservice need that continuously but it doesn't affect the act of deploying)