Ziggurat
A .NET library to create message consumers. (by rafaelpadovezi)
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.
Ziggurat
Posts with mentions or reviews of Ziggurat.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-13.
- Consistência de dados e padrão Outbox
-
📦 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.
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.