AsyncEx VS silverback

PS: You may want to look at the other in-memory concurrency structures available. You may find something that perfectly fits the specific problem you are trying to solve. https://learn.microsoft.com/en-us/dotnet/api/system.threading?view=net-7.0, https://learn.microsoft.com/en-us/dotnet/api/system.collections.concurrent?view=net-7.0, and https://github.com/StephenCleary/AsyncEx

Async Lock.

If you haven't seen it before, there's an excellent async util library on nuget by Stephen Cleary called Nito.AsyncEx.Coordination. It contains a number of classes to help with async synchronization, giving options beyond SemaphoreSlim. It might be worth checking out.

and if you need ReaderWriterLock behavior in an async context, Stephen Cleary has an implementation

Pessimistic concurrency - you can use something like AsyncLock from Nito.AsyncEx package, to lock around each db access.

This library has class that will allow you to safely run async code in Sync-context enabled environment.

Nito.AsyncEx:

MassTransit, SlimMessageBus, and SilverBack abstract interactions with message queueing systems. Some of what you are trying to do (I didn't read it deep enough to know exactly what you're using the queue for) would be done as a queue configuration instead (e.g. ordering, de-dupe, etc.).

You can look here to have an idea of the tools and the pipeline (I also use azure devops): https://github.com/BEagle1984/silverback

I tend to declare the parameter as IReadOnlyCollection because I can safely iterate without extra allocations. I know you could just do a ToList by default but it would mean allocating a few arrays in the process, in worst case. You could be smarter and check if the IEnumerable can be casted to IReadOnlyCollection and perform a ToList only when needed, this would be the most flexible implementation. I sometimes create an extension method for this: https://github.com/BEagle1984/silverback/blob/master/src/Silverback.Core/Util/EnumerableAsCollectionExtensions.cs.

I strongly believe in CQRS and all my projects implement it (using a mediator etc. - I even built a framework myself for those stuff https://silverback-messaging.net).

Yes we do use Kafka in the company I work for. I built a library/framework on top of Confluent.Kafka for it. Check it out: https://silverback-messaging.net/ or https://github.com/BEagle1984/silverback.

Silverback! https://github.com/BEagle1984/silverback / https://silverback-messaging.net

😁 Nope, not really. The code displayed is from my “hobby” project: https://github.com/BEagle1984/silverback.

By the way, if you are looking for a good/great library to interact with the brokers -> https://github.com/BEagle1984/silverback