Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
Since version 7.2, in an effort to improve the performance on the publishing side, we have tasked the .NET thread pool with handling message publishing. However, because tasks in the thread pool are not guaranteed to be executed in order, and because ensuring linear publishing makes sense in certain use cases, we will revert to linear publishing starting with this version. At the same time, we are introducing a new option, EnablePublishParallelSend
, to allow users to enable parallel message sending.
EnablePublishParallelSend
to support enable parallel message sending. (#1480) Thanks @yang-xiaodongFull Changelog: https://github.com/dotnetcore/CAP/compare/v8.0.1...v8.1.0
DotNetCore.CAP.Dashboard removed DefaultAuthenticationScheme
, UseChallengeOnAuth
, DefaultChallengeScheme
and AuthorizationPolicy
options .
Now CAP dashboard auth/authz mechanism to leverage the "ASP.NET Core" way of doing it, see #1428.
FallbackWindowLookbackSeconds
option to configure the retry processor to pick up the backtrack time window for Scheduled or Failed status messages. (#1455) Thanks @apatoziProducerThreadCount
configuration option. Now automatically send task managed by the .NET thread pool. (#1380)AutoDeleteOnIdle
option for Azure Service Bus. (#1350) Thanks @StevenDevooghtFailedRetryInterval
. (#1359) Thanks @li-zheng-haoUseDispatchingPerGroup
option. (#1356) Thanks @sampsonye @li-zheng-haoFull Changelog: https://github.com/dotnetcore/CAP/compare/v7.1.1...v7.1.2