A truly event driven web
Ever been to one of those aggregating search sites where the result list is populated in chunks, rather than all at once? Ever wondered how it works? Event driven sites are robust, extendable - and if you’re on a messaging system like RabbitMQ and a .NET client like RawRabbit, it is pretty easy to get started.
Making sense of all those logs
It is indeed a change of mindset to break up larger applications into smaller, contained services. One aspect of the transition, that is often somewhat overlooked, is the log file havoc that often sneak up on you when you least want it.
No such thing as perfect code
The date for the next major release of RawRabbit is drawing nearer. It is more than a year ago since I decided to implement a .NET Core1 client for RabbitMq. During this time, I’ve discovered some differences between developing a library and an application.
I really wonder how much Microsoft payed for that domain. ↩
A few days ago, I asked the RabbitMq community for input on what is missing in todays high level .NET clients. One of the topics that came up was the ability to control the concurrency of messages consumed. This has been discussed before, so I thought I’d implement it for RawRabbit.