Akka.Streams.Kafka
CAP
| Akka.Streams.Kafka | CAP | |
|---|---|---|
| 1 | 7 | |
| 67 | 6,445 | |
| - | 0.5% | |
| 6.3 | 8.7 | |
| 2 days ago | 6 days ago | |
| C# | C# | |
| Apache License 2.0 | MIT License |
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.
Akka.Streams.Kafka
-
Microservices: DDD, CQRS, ES... and gRPC
I've used a lot of the akka stuff (in Scala, not .NET) and actually would recommend the higher abstracted libraries. For example Akka.Streams.Kafka would be my go-to for setting up a kafka producer and consumer model for an event driven architecture. A framework that supports message queues (masstransit, rebus) would also be helpful in certain cases, as queues and transaction logs have a tiny bit different use cases.
CAP
-
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?
Confluent's .NET Client for Apache KafkaTM - Confluent's Apache Kafka .NET client
MassTransit - Distributed Application Framework for .NET
craftsman - A .NET scaffolding tool to help you stop worrying about boilerplate and focus on your business logic 🚀
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Reactive-kafka - Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka.
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
Pulsar4s - Idiomatic, typesafe, and reactive Scala client for Apache Pulsar
Rebus - :bus: Simple and lean service bus implementation for .NET
EasyNetQ - An easy to use .NET API for RabbitMQ
Brighter - A framework for building messaging apps with .NET and C#.
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
AdaskoTheBeAsT.MediatR.SimpleInjector and AdaskoTheBeAsT.MediatR.SimpleInjector.AspNetCore - MediatR extension to SimpleInjector