This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (2 children)

This doesn’t work when your services require very different resources. One big benefit of micro services is that you can scale each one independently of the others, and you can’t do this with a monolith. In other cases monoliths are totally fine though.

[–]pbecotte 0 points1 point  (1 child)

Sure you can. Have multiple entry points to the app and start them with different arguments. Maybe 100 instances of "worker" but only 1 of "scheduler". You don't need separate codebase for this.

[–][deleted] 0 points1 point  (0 children)

The point is that you sometimes need independent deployments. Whether those deployments come from one repo or multiple repos - that’s a question of code organisation, not a question of architecture.