Skip to content

v0.45.2877

Compare
Choose a tag to compare
@rasmus rasmus released this 28 May 17:41
  • Breaking: Asynchronous subscribers are now disabled by default, i.e.,
    any implementations of ISubscribeAsynchronousTo<,,> wont get invoked
    unless enabled
    eventFlowOptions.Configure(c => IsAsynchronousSubscribersEnabled = true);
    
    the ITaskRunner has been removed and asynchronous subscribers are now
    invoked using a new scheduled job that's scheduled to run right after the
    domain events are emitted. Using the ITaskRunner led to unexpected task
    terminations, especially if EventFlow was hosted in IIS. If enabling
    asynchronous subscribers, please make sure to configure proper job
    scheduling, e.g. by using the EventFlow.Hangfire NuGet package. The default
    job scheduler is InstantJobScheduler, which executes jobs synchronously,
    giving a end result similar to that of synchronous subscribers
  • Breaking: InstantJobScheduler, the default in-memory scheduler if nothing
    is configured, now swallows all job exceptions and logs them as errors. This
    ensure that the InstantJobScheduler behaves as any other out-of-process
    job scheduler