Time has come to encapsulate the consuming part a bit, and in this post we will move this to something called NatsObservable which extends IObservable<IOp> and therefore lets you observe incoming ops from a Nats server. Using ReactiveExtensions.Net [https://github.com/Reactive-Extensions/Rx.N…
Daniel Wertheim
I just published a post [https://danielwertheim.se/simple-incoming-op-parser-for-nats-in-c/] where I describe the OpParser and which lets you consume downstream ops from a NATS [http://nats.io/] server. On demand, lets show how to use it with a NATS server to get a long running subscriber. All po…
Daniel Wertheim
Instead of a big blog post I'll continue to write smaller parts in my journey with Nats. Feels like it rimes better with the philosophy of Nats. So, this time, lets look at a simple parser that parses a downward stream from a Nats server to a client in C#. The implementations shown will change…
Daniel Wertheim
Just had a quick glance at NATS [http://nats.io/] and its protocol [http://nats.io/documentation/internals/nats-protocol/] and I went: OMG, it's like so simple and therefore so tremendously beautiful. Why? I told you. It's simple. And I can read it. As in read it and understand it without ha…
Daniel Wertheim
Routemeister in it self is designed to be small and solve one thing well. How-ever, the powers of it is still great. Lets presume you need a router that routes messages to one particular instance of an object. This could be useful for e.g. aggregating something based upon a bunch of events. Define…
Daniel Wertheim