c# - Domain Events Implementation -

we starting ddd, , need implement domain events (des). thinking "developping our own system" vs "prototyping exiting framework". know things des. need have real-life feedbacks features should expected such system, before taking decision :

• should des stored , duplicated in each domain centralized event-store, before being consumed (for maintenance , logging purposes) ?
• do domains pick events centralized event-store (if any), or need kind of orchestrator dispatching des ?
• if use relational database storing domains data (we know should ignore when desiging business logic), relational database fit des, or should prototype nosql database ?
• do need implement tools ensure events propagated target domains ?

i know there many questions here, summarize ask :

based on experience, key-features can expect "theorical des system" ? have develop own implementation, does-it make sense ? service-bus meet our needs ?

i've built couple of libraries purpose and... depends. can go simplest solution closed udi dahan's example or durable service bus.

i'd recommend durable service bus approach can't recommend specific product since i'm using own concoction. durable part important, ensures event still handled if app crashes.

and important thing durable bus, command/event handlers need idempotent. bus guaranties delivery @ least once, need prepared handle same message multiple times.