Hi,
I practice DDD in my project.
Let's assume the boundedcontext IdentityAndAccessContext and MeetingContext.
Both contexts deal with the following terms:
User
class.Participant
class. (let's forget Creator
for the example).Participant
represents the user in Meeting bounded context.
First, a User
has to be created, leading to a UserCreatedEvent
.
Then, in order to apply eventual consistency between those bounded contexts, the message is stored in the IdentityAndAccessContext and then sent through helps to an event listener and message queuing (still in the IAC context) to the MeetingContext, in order to create automatically the corresponding Participant
.
It sounds like a good DDD design (IMO), however I come across an issue with this webapp's workflow:
Participant
values...and that's the issue:How to deal with this case?
Making the user wait before a notification of consistency? Bad UX no?
Inserting the Participant
values in the same transaction of the User
? ... violating Bounded contexts concept, wouldn't it?
--
You received this message because you are subscribed to the Google Groups "DDD/CQRS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dddcqrs+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.