silverback
Silverback is a simple but feature-rich message bus for .NET core (it currently supports Kafka, RabbitMQ and MQTT). (by BEagle1984)
CAP
Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern (by dotnetcore)
silverback | CAP | |
---|---|---|
10 | 7 | |
246 | 6,438 | |
- | 0.5% | |
7.1 | 8.7 | |
11 days ago | 10 days ago | |
C# | C# | |
MIT License | MIT License |
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.
silverback
Posts with mentions or reviews of silverback.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-24.
-
C# Complex Web Scraper: Looking for feedback / code review?
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.).
-
Modern StyleCop alternative? Advice appreciated.
You can look here to have an idea of the tools and the pipeline (I also use azure devops): https://github.com/BEagle1984/silverback
-
How can I avoid IEnumerable multiple iterations? Is it bad to cast IEnumerable --> ICollection --> IEnumerable to perform validation?
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.
-
Should I be using .AsNoTracking() on my read only queries?
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).
-
How are you using Kafka?
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.
-
NServiceBus vs CAP vs Brighter vs MediatR+Hangfire vs ...
Silverback! https://github.com/BEagle1984/silverback / https://silverback-messaging.net
-
Here my simple battle-/workstation
đ Nope, not really. The code displayed is from my âhobbyâ project: https://github.com/BEagle1984/silverback.
-
Process to Process messaging system? (Any recommendations?)
By the way, if you are looking for a good/great library to interact with the brokers -> https://github.com/BEagle1984/silverback
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 silverback and CAP you can also consider the following projects:
MassTransit - Distributed Application Framework for .NET
Rebus - :bus: Simple and lean service bus implementation for .NET
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Confluent's .NET Client for Apache KafkaTM - Confluent's Apache Kafka .NET client
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
Gofer.NET - Easy C# API for Distributed Background Tasks/Jobs for .NET Core.
EasyNetQ - An easy to use .NET API for RabbitMQ
Brighter - A framework for building messaging apps with .NET and C#.