blankensteiner commented on issue #66: URL: https://github.com/apache/pulsar-dotpulsar/issues/66#issuecomment-748075520
Hi @worldbeater Thanks for reaching out! I'll try and answer the best I can. Turning back time a little the situation was that there were no .NET clients for Apache Pulsar. Unaware of each other I and the creator of pulsar-client-dotnet started working on one. I implemented it in C# and he is using F#. After some time Danske Commodities (where I work) allowed me to use company time on DotPulsar. At some point, Apache Pulsar reached out and asked if we would donate DotPulsar and we (Danske Commodities and I) happily did so. Now DotPulsar is owned by the Apache Software Foundation and is the official .NET client for Apache Pulsar. There are currently 12 contributors to DotPulsar, where I'm the only one from Danske Commodities, so we actually have a community around DotPulsar and you are most welcome to join the slack channel. At Danske Commodities we are 30 developers, but we are currently using RabbitMQ which is why there hasn't been much activity on DotPulsar and some features are missing. However, we have just gotten a staging and production cluster up and running (this month) and as of January, we will release it to the developers. I hope this means more contributors and more time for DotPulsar since we will ourselves be needing some of the missing features. One difference between the two clients is perhaps the dependency approach. I would much prefer DotPulsar to be modular so that you only bring in what you need. Meaning that if you want snappy compression it should be by using a NuGet package called something in the lines of DotPulsar.Compression.Snappy, instead of having just the DotPulsar NuGet package that brings in dependencies for snappy, avro, k4os, NSec, zlib, Zstd, and so on. Hope that answers your question :-) Best regards db ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
