Domain Events, a Domain-Driven Design (DDD) pattern, provide a way to decouple your code. Rather than hard-coding a series of steps that must be completed in response to a particular action a user takes, that action can raise an event. Handlers for that event can be added without changing the code responsible for raising the event, resulting in a more extensible design. Coupled with SignalR in the UI layer, domain events can trigger updates to the application without the user having to refresh the application.

2. http://bit.ly/PS-ssmith

3. I’m right
here!

4. • Domain Events not in original DDD book (2004)
• Covered by Fowler in 2005
• Eric Evans published article on it in 2010

15. http://martinfowler.com/eaaDev/EventSourcing.html

21. http://bit.ly/PS-ssmith
http://martinfowler.com/eaaDev/DomainEvent.html
https://domainlanguage.com/newsletter/2010-03/
https://lostechies.com/jimmybogard/2010/04/08/strengthening-your-domain-domain-events/
http://www.udidahan.com/2009/06/14/domain-events-salvation/
https://lostechies.com/jimmybogard/2014/05/13/a-better-domain-events-pattern/
http://www.jayway.com/2013/06/20/dont-publish-domain-events-return-them/