NET-Microservices-Architecture-for-Containerized-NET-Applications-(Microsoft-eBook)

in enterprise applications it is more important not to couple the server side to the client side than to follow the DRY principle

In order to maintain separation of aggregates and keep clear boundaries between them, it is a good practice in a DDD domain model to disallow direct navigation between aggregates and only having the foreign key (FK) field

In fact, if your internal microservices are communicating by creating chains of HTTP requests as described, it could be argued that you have a monolithic application, but one based on HTTP between processes instead of intraprocess communication mechanisms.