BergPerformanceProfiler
NetMQ
BergPerformanceProfiler | NetMQ | |
---|---|---|
1 | 2 | |
0 | 2,905 | |
- | 0.8% | |
0.0 | 5.7 | |
over 4 years ago | 7 days ago | |
C# | C# | |
- | GNU General Public License v3.0 or later |
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.
BergPerformanceProfiler
NetMQ
- New network library in the works
-
Question: Best way to do interprocess communication?
Lots of answers here about named pipes but there are less verbose and time consuming ways to. Having just done this, for a very similar reason to yours, I highly suggest NetMQ, https://github.com/zeromq/netmq
What are some alternatives?
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
MassTransit - Distributed Application Framework for .NET
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
DotNetty - DotNetty project – a port of netty, event-driven asynchronous network application framework
EasyNetQ - An easy to use .NET API for RabbitMQ
Kafka Client
Gofer.NET - Easy C# API for Distributed Background Tasks/Jobs for .NET Core.
Enexure.MicroBus - MicroBus is a simple in process Mediator for .NET
Kafunk
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern