protobuf-net.Grpc
MassTransit
protobuf-net.Grpc | MassTransit | |
---|---|---|
3 | 19 | |
841 | 6,550 | |
1.1% | 1.4% | |
2.2 | 9.4 | |
3 months ago | 6 days ago | |
C# | C# | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
protobuf-net.Grpc
-
GRPC and proto files: create common library for output, or output .protos to every microservice project?
In any case, I suggest you check protobuf-net.Grpc which prevent you from having to write proto files altogether.
-
gRPC Development experience in modern .NET
Code-first grpc is awesome. Just check out this lib: https://github.com/protobuf-net/protobuf-net.Grpc
-
What technology to use?
grpc seems to be the obvious choice here. i use the following library which makes grpc use a breeze. no need to mess around with proto files. https://github.com/protobuf-net/protobuf-net.Grpc
MassTransit
-
Easy to use library for RabbitMQ in dotnet core.
What would be the benefits of using your library instead of something like MassTransit?
- Consistência de dados e padrão Outbox
-
MassTransit with MSMQ vs RabbitMQ
However, I found this discussion on MT github: https://github.com/MassTransit/MassTransit/discussions/2546
-
Agnostic Messaging Provider - Azure/Google/AWS
MassTransit (https://github.com/MassTransit/MassTransit)
-
What's the deal with "hosts" in console applications now?
I really like https://masstransit-project.com/. I use it with both RabbitMQ and Azure Service Bus
-
📦 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.
- Do I need message queues for sending emails/texts via services like SendGrid, AWS SES, Twilio etc.? How do you decide if you need message queues or not? What questions do you ask yourself?
-
Best .net open source microservice based project?
I actually found the MassTransit samples really enlightening. https://masstransit-project.com/
-
Hello my company is trying to port from PHP to C#. Currently we want to port worker an example you execute cli command which is long running command which consumes messages from Rabbit Mq. How do you suggest that we do it in Dotnet way?
https://masstransit-project.com/ - Mass Transit might help, it's designed to make handling messages in .net easier and supports Rabbit Mq - might be worth a look
-
.NET application stuck and on processing bus messages because of possible other activity in the console app? How can I debug?
Look into IHostedService or use something like MassTransit
What are some alternatives?
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
Rebus - :bus: Simple and lean service bus implementation for .NET
Protobuf.NET - Protocol Buffers library for idiomatic .NET
EasyNetQ - An easy to use .NET API for RabbitMQ
protolock - Protocol Buffer companion tool. Track your .proto files and prevent changes to messages and services which impact API compatibility.
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+