I recently had an interaction with an NServiceBus customer and noticed that they are pushing the log of their import process all the way to the UI. While this may be normal in some cases, but why do you put all the technical details, including exceptions, stack trace, in case of errors in that customer facing log window? The answer was: it is hard for us to gather all the relevant information from a distributed process that’s running in a handful of microservices. When something goes wrong, it is hard for us to gather all the relevant information.

It all boiled down to this: while each individual service capture all the detail of a successfull and failed job, the logs go into individual log files on those services. It is hard to connect these logs across different services. In a nutshell, distributed logging is hard. But does it have to be? Continue reading

NServiceBus Sagas are a powerful feature that would allow you model long running processes without managing the state on your own or having to juggle correlating messages. Since they manage the state for you and messaging systems being distributed and things running concurrently, they also do concurrency control via Optimistic Concurrency.

Continue reading

You may have noticed in NServiceBus release note that there are a few new transports available on v4.0. This means you no longer need to choose MSMQ as your transport and can choose from other well reputed queue engines such as ActiveMQ and RabbitMQ. Continue reading

If you’ve been following this blog, you’ve noticed that it has gone radio silent for some time. The reason was that I was spending most of my time on developing ServiceInsight application. I’m happy to announce that Beta-2 is now available and you can grab it from here. Continue reading

When working on a project using NServiceBus, we came up with an interesting requirement. The messages in the queue should be processed only in certain time frames. The reason is that message handler is making a webservice call and the other party is only available at certain times and system is not even allowed to make a call during the outage window. Continue reading

While using NServiceBus on the first engagement at Readify, we had an interesting configuration. Development environment has a shared database which runs on a server but when creating the backend application, we’re running NServiceBus on our local developer machines. Continue reading