Savvas Kleanthous

Hey all, Just to note that there is a very specific reason why the aggregate is the actual consistency boundary: in the absence of distributed db transactions (which is the...

Just to note that I am very much OK with pragmatism, especially considering that most of what we have are guidelines and heuristics. However, in this case above we have...

Specifically about domain services and where they are called I think the fact that the services throw exception is something you can utilize to allow to deal with errors as...

Regarding uniqueness of username, it depends if it's simple or not. For example you could use the username as a natural primary key (which it is), but if combined with...

One thing to note though, it doesn't really matter where the "detector" is called from, it matters whether some data used in the decision-making process are checked for concurrency at...

With point 3 in https://github.com/webdevilopers/php-ddd/issues/60#issuecomment-901145964 you don't need to change 2 aggregate roots in one transaction. You'll have one aggregate that _only_ guarantees the "usernames have to be unique" and...

Hey @smbecker, thank you for raising this issue. Unfortunately, in the past it seems that plantuml doesn't always honour skin parameter settings. I am not sure this is one of...

If you're running this locally, one thing you could try is update plantuml to its latest version and see if that works.

@MerrionComputing The idea is that you put the domain name in metadata 2. Note that this doesn't necessarily have to be `FQN = (metadata 2) + (metadata 1)`. Doing that...

@ylorph That's an interesting point. A couple of thoughts on that: 1. Having the service name (metadata point 2) contain the platform may be a good idea. You would use...