Code rant

I’ve been a long time fan of IoC (or DI) containers ever since I first discovered Castle Windsor back in 2007 . I’ve used Windsor in every m...

Since it’s very first version, EasyNetQ has allowed you to subscribe to a message simply by providing a handler for a given message type ...

From version 0.22, EasyNetQ supports a new message pattern: Send/Receive. Whereas the Publish/Subscribe and Request/Response patterns are...

A common feature request for EasyNetQ has been to have some way of implementing a command pipeline pattern. Say you’ve got a component that ...

Consumer cancellation has been a requested feature of EasyNetQ for a while now. I wasn’t intending to implement it immediately, but a pull ...

TL:DR: Exchange and queue names used to have ‘.’ replaced with ‘_’. From version 0.18 this is no longer the case. Yesterday I announced ve...

From version 18.0 of EasyNetQ , you can now subscribe to an interface, then publish implementations of that interface. Let's look a...

My intensive work on EasyNetQ (our super simple .NET API for RabbitMQ ) continues. I’ve been taking lessons learned from nearly two years o...

If you are programming against a web service, the natural pattern is request-response. It’s always initiated by the client, which then waits...

Publisher confirms are a RabbitMQ addition to AMQP to guarantee message delivery. You can read all about them here and here . In short t...