Darker
The query-side counterpart of Brighter (by BrighterCommand)
CAP
Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern (by dotnetcore)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Darker
Posts with mentions or reviews of Darker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-08.
-
Should I null-check every database get by id calls?
Sample untested code using Darker
-
Project Layout Format?
Consider the CQRS pattern as a replacement to repository/service. Because it's not that complicated, I ended up rolling my own implementation (ICommand, ICommandHandler, ICommandDispatcher, equivalents for Query, and then some DI to tie them together.) There are quite a few Nuget CQRS packages and lots of example implementations on the web. I also just heard about Brighter and Darker but I haven't had a chance to try them out yet. Sounds pretty interesting.
CAP
Posts with mentions or reviews of CAP.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-22.
-
Mechanism for managing faulty consumer in asynchronous event broadcast in microservices / modular monolith
You might want to implement the outbox pattern. There’s a decent library that’ll help and is really easy to integrate. In particular, I’d look at using the transaction functionality
- Consistência de dados e padrão Outbox
- Message Queueing
-
Is there MQ that is using only redis for dotnet?
This might be of interest https://cap.dotnetcore.xyz/
-
📦 Data consistency, outbox pattern and idempotency in a microservice architecture
There are many libraries in .NET that helps you implementing the outbox pattern like: MassTransit, NServiceBus, CAP. Talking about idempotency, a special mention to a specific lib from a big friend that runs on top of CAP which is called Ziggurat.
-
Which library do you use for message bus abstraction?
CAP is your friend https://github.com/dotnetcore/CAP
-
14 .NET packages I always recommend
Correct but I would actually consider CAP instead. The primary reason is that CAP implements the outbox pattern out-of-box where you would need to implement this yourself with Hangfire.
What are some alternatives?
When comparing Darker and CAP you can also consider the following projects:
Brighter - A framework for building messaging apps with .NET and C#.
MassTransit - Distributed Application Framework for .NET
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
CQRSlite - A lightweight framework to help creating CQRS and Eventsourcing applications in C#
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
Rebus - :bus: Simple and lean service bus implementation for .NET
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
EasyNetQ - An easy to use .NET API for RabbitMQ