Michal Bičan

DomainEventPublisher shouldn't stop at exception

1

Since IDomainEventPublisher.PublishAsync() is called after events are already successfully persisted into eventStore all event subscribers should be notified about event. Currently if the first subscriber throws an exception the other...

Automatically add saga id to event metadata + create default SagaLocator

2

In documentation about sagas there is this thing about storing saga-id into event metadata. It looks intuitive but it doesn't work out of the box :-(. I would like to...

AggregateSaga doesn't publish commands published from command handler method

4

AggregateSaga is also an aggregate so it can receive commands and even be created by a command. The problem is when in AggregateSaga command handler method I use AggregateSaga.Publish() protected...

Reliable saga published commands redelivery after crash

1

after reliable event redelivery in case of crash #439 is implemented we could use it for reliable saga published commands redelivery. That would require to atomically store saga produced commands...