Thank you for the insightful talk! I appreciate the points made, but I respectfully disagree with Oliver’s statement around minute 17 regarding the necessity of using jMolecules to define aggregate roots. In my experience with Spring Data JPA and Domain-Driven Design (DDD), we can effectively define aggregate roots by leveraging the `AbstractAggregateRoot` class provided by Spring Data, without needing to rely on jMolecules. This approach works well for managing domain events and maintaining the boundaries of the aggregate in a clean, straightforward manner.
Great content as always!
Thank you for the insightful talk! I appreciate the points made, but I respectfully disagree with Oliver’s statement around minute 17 regarding the necessity of using jMolecules to define aggregate roots. In my experience with Spring Data JPA and Domain-Driven Design (DDD), we can effectively define aggregate roots by leveraging the `AbstractAggregateRoot` class provided by Spring Data, without needing to rely on jMolecules. This approach works well for managing domain events and maintaining the boundaries of the aggregate in a clean, straightforward manner.