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)

Transporting large payloads


When using any message queuing system, you will discover that very large messages are not a good idea. With MSMQ, there is a hard limit of 4 MB per message.

This may seem like a lot, but consider the situation we mentioned in Chapter 1, Getting on the IBus, where we're processing images for our clients. You might be able to squeeze most images into an MSMQ message, but you shouldn't bank on it. These days, 12-megapixel cameras that create 2.5 MB JPEG images are fairly commonplace, and once the message serializer Base64 encodes the byte array into the message, you're looking at 3.3 MB. That's way too close for comfort considering the average number of megapixels has nowhere to go but up. Now consider the 256 KB limit on Windows Service Bus Queues, or the 64 KB limit on Windows Azure Queues!

Other queuing systems don't have a hard limit, but that doesn't mean creating huge messages is a good idea! Because of the implications of shuffling all these messages around...