Skip to content

Development of a EventDomain dispatcher using a simple Observer pattern in order to deliver and receive domain events

Notifications You must be signed in to change notification settings

truar/eventDomain

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Event domain

Notes

  • Listener of domain events are :

    • Application Services
    • Exposition Resources classes (to enjoy Spring and proxy management)
  • Domain events are published from domain classes

    • Is it always true ?

Questions

  • Should a DomainEvent be handle in the same transaction ?
    • Depends on business ? What are the rules ?
  • What happens if a service listening for events throws an Exception ?
    • Should it rollback everything ?
    • Should it be skipped ?
    • Depends on business requirements ?
  • Should an event treated asynchronously ?
  • Is it a good practice to publish an event in the aggregate constructor ?
    • should it be before / after save ? Depends on what criteria ?

About

Development of a EventDomain dispatcher using a simple Observer pattern in order to deliver and receive domain events

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages