tag:blogger.com,1999:blog-6272686660327136275.post3876642412844598113..comments2014-12-15T03:13:20.972+01:00Comments on DDDSample.Net: Application Events vs Domain EventsSzymon Pobiegahttp://www.blogger.com/profile/15921684506692120835noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6272686660327136275.post-2234803237803923942009-10-08T21:27:40.228+02:002009-10-08T21:27:40.228+02:00Hello, that's a very interesting analysis. The...Hello, that's a very interesting analysis. The possible confusion between domain events (event as domain elements) and application events (transient and an asynchronous execution mechanism) was something that we noted a while ago and decided to rename to sound a little less domain-like:<br /><br />SystemEvents.notifyOfCargoHandling()<br /><br />System events is a term that occurs elsewhere in the litterature, so that was selected in favor of application events.<br /><br />We use domain events to model (some) things that happen in the domain (cargo shipping), that a domain expert would care about and that is relevant for the problem we're trying to solve (tracking cargo). System events on the other hand are used to let some part of the application know that something has happened in another part of the applicaiton, and to allow interested parties to act upon those events.<br /><br />Peter Backlund<br />DDDSample Lead developerPeter Backlundhttps://www.blogger.com/profile/17377084852220577629noreply@blogger.com