Book Image

Learning NServiceBus

By : David Boike
Book Image

Learning NServiceBus

By: David Boike

Overview of this book

<p>Web service-based systems are designed using Remote Procedure Call (RPC) techniques. This technique is effective; however, this method creates problems with scalability and reusability as fault tolerance is inherently hindered by the RPC principles. This book helps you to overcome this problem by introducing you to the principles of messaging and SOA to build scalable and reliable systems, that are easy to extend and maintain.</p> <p>"Learning NServiceBus" is your essential guide to becoming a messaging guru. The book details the process of building a software system based on the SOA principles. From sending a simple message to publishing events, this book covers everything you need to know to understand and implement an SOA-based message driven systems.</p> <p>"Learning NServiceBus" will teach you how to use publish/subscribe to create an Serivce Oriented Architecture. We will then look how to manage and extend that architecture. Through the course of the book, you will build reliable systems which will automatically compensate for failures. You will also learn to build complex yet testable business processes which will make batch processes seem outdated. By the end of the book, you will realize that SOA is much more than just web services.</p>
Table of Contents (15 chapters)

Monitoring


NServiceBus makes it easy to monitor the performance of any endpoint that has the performance counters enabled, which includes any endpoint installed with the production profile. After having installed NServiceBus and a service with counters enabled, you will find these counters in the NServiceBus category in the Windows Performance Monitor:

  • Number of message failures per second

  • Number of messages pulled from the input queue per second

  • Number of messages successfully processed per second

  • Critical time

  • SLA Violation Countdown

The last two are especially interesting. critical time is the age of the oldest message in the queue, or in other words, the length of the queue's backlog in seconds. This is important because it is how business stakeholders will judge the capability of your system. In a messaging system the business probably doesn't care what your overall throughput is; what they really care about is that their work gets done within a length of time that they deem reasonable. Critical...