I like the rubric of, "If you have a people scaling problem or a performance scaling problem then you maybe need a microservice" Meaning, if there are too many

I like the rubric of, "If you have a people scaling problem or a performance scaling problem then you maybe need a microservice" Meaning, if there are too many cooks in the codebase and it's slowing down delivery, maybe use a microservice (which this reply is effectively calling out). The latter, if there is a hot place(s) in the code that needs to scale independently, maybe use a microservice. Any microservice can be represented as a library or dependency, design the code well and breaking things out shouldn't be terrible. See Moduliths https://github.com/odrotbohm/moduliths https://github.com/odrotbohm/moduliths