You are right but from a different context. In a well thought out microservice architecture, you will not have business logic scattered across multiple services.
We have had instances of microservice architecture where doing one change required changes in 4 different microservices defeating the whole point. Obviously this is bad.
“ In a well thought out microservice architecture, you will not have business logic scattered across multiple services.”
A “well thought out” architecture that holds up over years is a pipe dream. There will always be changes that require a rethinking of the whole system.
Yes that's the tradeoff. Over time your architecture degrades and you need to rethink the services. But good part is that migration is simpler and less risky when you are just making changes to few microservices.
We have had instances of microservice architecture where doing one change required changes in 4 different microservices defeating the whole point. Obviously this is bad.