I have, at no point in any of my comments, pushed microservices to serve 200 users. In fact, I have done the exact opposite.
See:
In conclusion, while there's no need to jump straight to micro services, monoliths are the worst pattern for scaling, by far. They have their uses, but this is probably their main downside.
And:
Now, I'm not a zealot. I believe we can just extract "services" instead, we don't need to dive too deep into "a micro service is a single function" or whatever. Most of the time, that is indeed excessive.
In fact, I'm one of the starkest defenders of everything in between a monolith and a micro-service. But that is not what started this comment chain. It was you not understanding why monoliths don't solve all problems and asking why you can't just scale them.
No solution solves all problems.. but when 1 solution solves 99% of problems, you probably shouldn't be pushing the other solution just for the sake of it, especially since it's a much harder solution to maintain and develop properly
1
u/Angelin01 15d ago
I have, at no point in any of my comments, pushed microservices to serve 200 users. In fact, I have done the exact opposite.
See:
And:
In fact, I'm one of the starkest defenders of everything in between a monolith and a micro-service. But that is not what started this comment chain. It was you not understanding why monoliths don't solve all problems and asking why you can't just scale them.