[akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

2014-12-18 Thread Vaughn Vernon
These are all really great questions. I will provide answers as I understand them and as things currently stand. In another thread Roland discusses the Akka roadmap for the next half year. It's possible that some things could change between now and then, so I can't say that this is long-term

Re: [akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

2014-12-18 Thread Richard Rodseth
Hi Vaughn Thanks so much for replying. I have your excellent book and the Blue Book, but obviously I'm still a bit unclear on some things. So you are giving unique identity to Domain Events? That sounds less like Event Sourcing already. While that can be done (and my book discusses it), it

Re: [akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

2014-12-18 Thread Vaughn Vernon
If you are doing Event Sourcing the Domain Events are both your state and the means by which others are notified of changes. Because with Event Sourcing you need to create new events for everything that happens in your Aggregates you may not want all of those events to be published to

Re: [akka-user] Re: Domain Events, Aggregate Persistence Events and cross-aggregate consistency

2014-12-18 Thread Richard Rodseth
It's not obvious to me that Alerts are part of the Monitor aggregate, but perhaps they are, with the in-memory model containing only the last alert, and a Read Model Projection, to use the term in Appendix A, to allow querying of alerts. On Thu, Dec 18, 2014 at 1:38 PM, Vaughn Vernon