I'm currently adding support for request-response message pattern in MyNatsClient. And as it turns out, it's really simple, much thanks to having it being based around Observables and thereby supporting Reactive Extensions. And, Yes. It does support DotNetCore. This will soon reach the client itself but for now lets look at how easy it wo…
Daniel Wertheim
NATS is designed to be always on and to guard the server/broker from misbehaving clients. So if your client somehow manages to send something that makes the message corrupt, the server will disconnect you. With the release of v0.6.0 of MyNatsClient, you now have the option to configure AutoReconnectOnFailure. So if the client gets to know…
Daniel Wertheim
Recently I just added support for .NET Core in MyNatsClient. And I also introduced the first of a few simplifying components that is coming to the MyNatsClient. All changes will be done to ease the construction of the upcoming NatsMessageBus which offer messaging over NATS, using subject conventions and message formatters and in-process r…
Daniel Wertheim
After my last performance tweaks (read more) I've finally become satisfied and have chosen to put MyNatsClient out on NuGet. There are some changes coming, like removing dependency on Newtonsoft's JSON.Net and adding support for SSL, but it's out and it's simple, fast and RX friendly! Why a new one when there's an official project? Becaus…
Daniel Wertheim
I finally managed to beat the official client in some metrics! This means that performance is finally good enough for a release!!! The big difference in the producer side was that MyNatsClient was calling Flush for each send, while the official client was doing this on a separate thread. There's some awesome constructs in the official cli…
Daniel Wertheim