design patterns - .net implementation of communication between aggregate roots in different bounded context -
this first time applying ddd concepts real world problem. i started 1 bounded context project relatively small. found myself classes identical i.e. similar names, similar properties different behaviour. starting think belong in different bounded contexts entities same , have different meaning in different context. supported fact application has 2 different user groups. i have done bit of reading on how 2 entities in different bounded context can communicate each other. think understand concept... have no idea how implement? there .net example somewhere? i.e. aggregate root in 1 bounded context publishing event aggregate root in bounded context? , aggregate root calling aggregate root in bounded context. and should each bounded context have own: service layer? repository , data layer? this may quote implementing domain driven design vaughn vernon. "perhaps common use of domain events when aggregate creates event , publishes it. publisher resides in module of m...