confluent-kafka-dotnet

Dotnet and java usually have similar libraries for most things, but sometimes it comes down to how different they are or what they support. Let's look at general distributed messaging abstractions. The most modern-featureful one for dotnet I know of is MassTransit: https://masstransit.io/documentation/concepts. You can see it supports a handful of queues and some interesting patterns. Compare this to the list of features in Apache Camel: https://camel.apache.org/components/4.4.x/eips/enterprise-in... Additionally, the _support_ of the libraries for common open-source (and closed-source infra) is usually vastly different: - https://pulsar.apache.org/client-feature-matrix/ - Small features being first party like https://github.com/awslabs/amazon-sqs-java-extended-client-l... vs https://github.com/raol/amazon-sqs-net-extended-client-lib - Mi

quite the contrary, people are quickly moving away from the .net framework towards .net core, which is now objectively better and moving at a fast pace. I help maintain a popular open source library for .net. We develop on MacOS using VS Code (only use Windows for testing) - the experience is good. We have many large customers (brands you would know), and .NET Core support is important to pretty much all of them. https://github.com/confluentinc/confluent-kafka-dotnet

I think you're being a bit unfair. I am not properly familiar with Guava, but aren't most things available in .NET's collections classes? A lot of what's in Commons is available in the .NET BCL. https://redis.io/clients#c looks fine to me (I'd probably pick the StackExchange client) NPgSQL seems to be the recommended library for Postgres. https://www.nuget.org/packages/CassandraCSharpDriver/ was updated in February. https://github.com/Microsoft/CSharpClient-for-Kafka starts to show some of the issues you're talking about - Microsoft aren't supporting this one anymore, but they point to https://github.com/confluentinc/confluent-kafka-dotnet which wraps librdkafka - seems sensible I'll definitely give you a point for the HTTP2/IIS issue - although there might be more technical reasons than you think for that. From what I recall, a lot of NE

My experience over the last few months has been v. good. Earlier (maybe even 6 months ago), my sentiment would have more mirrored that of the parent. The main downside at the moment is many of the packages on NuGet don't target dotnet core. The above opinion is based on my experience developing a Kafka client library (I use OSX / VS Code) for Confluent https://github.com/confluentinc/confluent-kafka-dotnet as well as a substantial side project.