But there can still be a benefit in disentangling a monolith where some of the parts have no interactions with other parts. I'm not a devotee of microservices,

But there can still be a benefit in disentangling a monolith where some of the parts have no interactions with other parts. I'm not a devotee of microservices, and most of my experience involves front-end web stuff. I've come across quite a few monoliths in that context that were more difficult to work with than they had to be because, for example, various 'services' had their db and view layers tangled up together even though they really didn't have anything to do with each other. A more 'microservice-y' approach would've made things much easier to work with. I do agree that a bunch of microservices that end up depending on each other doesn't necessarily improve much, though, and often actually causes problems.