webDEVILopers

> You can subscribe from the event stream and only publish messages from there. Going this way also allows you to rebuild and start from event 1 again. Thank you...

@Federkun also suggested the "Outbox pattern" (for NServiceBus): > Outbox is the way * https://twitter.com/Federkun/status/1292866987509665792 Thanks to twitter's algorithm one of the next tweets by @cer dealed with the same...

If I understand the pattern correctly then I think it can be achieved in the PHP world using the symfony messenger and the doctrine transport / transaction middleware. > If...

Great feedback @gquemener and @JulianMay, thanks! `Dispatch the events in the bus right after the aggregate transaction has been committed` - this was indeed our current approach so far. Most...

> ocramius has a blog post about it: https://ocramius.github.io/blog/on-aggregates-and-external-context-interactions/ I know that post for sure! Also discussed on twitter: * https://twitter.com/Ocramius/status/824352805318250504 And currently I prefer that approach too. As @Ocramius...

But I also agree on the suggestions made by @ludofleury : > If we focus on DDD role of aggregate root: consistency boundaries (nested elements VO or entities ensure their...

Thanks for your feedback and sorry again for the confusion. > "Pragmatism" is a cool word to solve all of our architectural problem :) I really like this "approach". I...

> I know this is slightly outside of the discussion where to use domain service, but I think it's quite an important point seeing the examples and discussion above. Actually...

> On the overlap employee contract,... > My first instinct would be designing a new AR. But as you rightly pointed out, it might be costly in a maintenance scenario....

> Regarding uniqueness of username,... I think this has become a "classic" example. 1. Use the username as primary key. Indeed this seems weird. 2. Store the username inside an...