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
A while back ago I started a project called MyCouch [https://github.com/danielwertheim/mycouch]. It's an async .Net driver for CouchDB [http://couchdb.apache.org/] and Cloudant [https://cloudant.com/]. Since I'm no longer an active user of neither CouchDB nor Cloudant, I think the project w…
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
Currently Routemeister does not come with built in support for a request-response scenario, much because I haven't decided on how this should behave and there hasn't been a need for it yet. But this doesn't stop you from implementing support for it. Routemeister is asynchronous, hence i…
Daniel Wertheim