Andrey Vorobyev

+1 ! Problem is actual for me too!

any progress here?

Also the way ``` If you really want to solve it in the domain, you need only 1 aggregate instance i.e. with a fix aggregate id (i.e. USER_EMAILS) ``` is...

Found similar question on stackoverflow https://stackoverflow.com/questions/31386244/cqrs-event-sourcing-check-username-is-unique-or-not-from-eventstore-while-sendin conclusion: there is no universal way how to do that. In most cases we have to put up with possible data inconsistency in such...

> This is why I said, you need 1 aggregate for all email addresses... > Or solve this outside of cqrs. > PS. sorry for not responding with a more...

> These type of errors should theoretically be catched via normal, error argument in the handle callback or as uncaughtException, i.e: > > ```js > process.on('uncaughtException', function (err) { >...

About ``` process.on('uncaughtException', function (err) { }) ``` I understand that we can use it in emergency cases if by some reason callback handler was not executed with error object...

``` When Designing this piece of code I discussed this with other persons. The decision was to always “punish” programmer errors this way, but feel free to suggest a PR....

> Always happy for a PR. currently we are at stage of investigating and collecting potential issues before the real start of development. As soon as we will do it...

any progress here?