Is microservices always good?
Blindly separating into small services and believe that will provide the code to be loosely coupled and easier maintained and deployed is a delusion.
It might give you delusion that it brings those benefits at first, but when business requirements changes, you might see the changes will cross cut the services as they are actually just indirectly tightly coupled.
What actually matter?
The well designed boundaries and coordination between etc. services with the hard work to deal with current business requirements and also prepare for the future by considering the cost between creating boundary vs delay decision (since over-engineering can cost more)
These considerations and leverages should be the factors driving architects to making decision on the architectural styles, principle and decisions.