I can add my experience to discussion: if you fail to clearly define the microservices domains, then you are going to hit a lot of problems. If you are in the need to implement too much orchestrations involving more and more domains, your architecture will easily become a mess. Anyway microservices world has its own design patterns that can be very handy, but never understimate the importance of put coupled domains in the same microservice.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can add my experience to discussion: if you fail to clearly define the microservices domains, then you are going to hit a lot of problems. If you are in the need to implement too much orchestrations involving more and more domains, your architecture will easily become a mess. Anyway microservices world has its own design patterns that can be very handy, but never understimate the importance of put coupled domains in the same microservice.