> How do you handle events with side effects (sending emails, for example), and ensuring they aren't triggered on replay when they shouldn't be? Someone else a

> How do you handle events with side effects (sending emails, for example), and ensuring they aren't triggered on replay when they shouldn't be? Someone else already addressed this, but to paraphrase: your application should be able to deal with duplicate events (and gracefully handle side-effects). > How do you handle randomness, like uuid generation? Are you referring to id generation and tagging in events (ie. aggregate id's)? If so, that'd be an application responsibility - you'd have to determine how to properly attach id's. Hmm. But that does bring up an interesting idea - what if we provided a way to "group" events and generate aggregate id's on your behalf. Maybe that's what you meant - it's an interesting idea. We currently don't do anything "extra" in regards to grouping events - we tag each individual event but that's about it.