Discussion about AggregateRoot and Invariant. #2
Description
Hello!!
While Watching domain-driven-design-fundamentals I realize that schedule class is kind of unnecessary .
we all knew that its for one single clinic means we don't have to persist cliicId and not other data is this class to save in db.
seems like this can be done with help of SchedulerService.
My Question is
Do we really need to have a schedule class to validate appointments overlaps ..?
in DDD words
do we really need to have a aggregateRoot for invariant to be applied ?
or it can be applied from a service.