Makes sense to get rid of Action scheduleHandler? about pluralsight-ddd-fundamentals HOT 1 CLOSED

The general guidance I've been following for years is, navigation properties only flow in one direction from the aggregate root to its children. Children then only have id references back to the aggregate root. The origins of this guidance were in fact at least in part due to common limitations with both ORM and Serialization libraries that would often blow up or otherwise misbehave if loops were present in the object graph (such as Schedule -> Appointment -> Schedule).

That said, while I still think it helps simplify aggregate generally, if you find that it's beneficial to include a navigation property in a child back to the parent, and there are no negative consequences in your app from doing so, then by all means do it. It's probably something I should revisit with the latest versions of .NET and EF Core, too, and see if the reasons for the original guidance are less relevant now.

from pluralsight-ddd-fundamentals.