Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Learning NServiceBus - Second Edition
  • Table Of Contents Toc
Learning NServiceBus - Second Edition

Learning NServiceBus - Second Edition - Second Edition

By : David Boike
4.8 (6)
Buy this Book
close
close
Learning NServiceBus - Second Edition

Learning NServiceBus - Second Edition

4.8 (6)
By: David Boike
Buy this Book

Overview of this book

If you are a .NET developer who wants to eliminate the problems related to defective third-party web service integration or batch job failures, then this is the book for you. It is also perfect for those of you who are new to NServiceBus and service-oriented architecture and would like to learn how you can streamline all of your development efforts.
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Getting on the IBus
Icon
1. Getting on the IBus
Icon
Why use NServiceBus?
Icon
Getting the code
Icon
Our first example
Icon
Creating a message assembly
Icon
Creating a service endpoint
Icon
Creating a message handler
Icon
Sending a message from an MVC application
Icon
Running the solution
Icon
Summary
2
2. Messaging Patterns
chevron up
Icon
2. Messaging Patterns
Icon
Commands versus events
Icon
Events
Icon
Message routing
Icon
Summary
3
3. Preparing for Failure
Icon
3. Preparing for Failure
Icon
Fault tolerance and transactional processing
Icon
Error queues and replay
Icon
Messages that expire
Icon
Auditing messages
Icon
Web service integration and idempotence
Icon
Summary
4
4. Hosting
Icon
4. Hosting
Icon
Hosting types
Icon
Assembly scanning
Icon
Choosing an endpoint name
Icon
Dependency injection
Icon
Message transport
Icon
Persistence
Icon
Message serialization
Icon
Transactions
Icon
Purging the queue on startup
Icon
Installers
Icon
Startup
Icon
Summary
5
5. Advanced Messaging
Icon
5. Advanced Messaging
Icon
Unobtrusive mode
Icon
Message versioning
Icon
Specifying the handler order
Icon
Message actions
Icon
Property encryption
Icon
Transporting large payloads
Icon
Exposing web services
Icon
Summary
6
6. Sagas
Icon
6. Sagas
Icon
Long-running processes
Icon
Defining a saga
Icon
Finding saga data
Icon
Ending a saga
Icon
Dealing with time
Icon
Design guidelines
Icon
Persistence concerns
Icon
Unit testing
Icon
Scheduling
Icon
Summary
7
7. Advanced Configuration
Icon
7. Advanced Configuration
Icon
Extending NServiceBus
Icon
Dependency injection
Icon
Unit of work
Icon
Message mutators
Icon
The NServiceBus pipeline
Icon
Outbox
Icon
Summary
8
8. The Service Platform
Icon
8. The Service Platform
Icon
ServiceControl
Icon
ServiceInsight
Icon
ServicePulse
Icon
ServiceMatrix
Icon
Summary
9
9. Administration
Icon
9. Administration
Icon
Service installation
Icon
Profiles
Icon
Managing configurations
Icon
Monitoring performance
Icon
Scalability
Icon
Multiple sites
Icon
Virtualization
Icon
Transport administration
Icon
Summary
10
10. Where to Go from Here?
Icon
10. Where to Go from Here?
Icon
What we've learned
Icon
What next?
11
Index
Icon
Index

Events

If you compare the following definition with that of a command, which was defined earlier in the chapter, you will notice that they follow the same general premise, but the differences are very important.

Note

An event is a message that is published from a single logical sender, and is processed by one or more logical receivers.

A command can be sent by any number of different senders. An event is only published by one logical sender. Sending a command sends one copy of a message to one receiver, and that receiver is the only entity that can process that command. In contrast, when an event is published, a copy of that message may be sent to dozens or even hundreds of subscribers, or maybe none if there are no subscribers.

This has even broader implications. While a command is an order to do something in the future, an event is an announcement that something has already happened. This is why commands are often named in the imperative, such as DoSomethingNowPleaseCmd, while events are...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Learning NServiceBus - Second Edition
End of Section 2
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon