Contents

• Getting Started
•     Overview
•     Video recordings about NServiceBus
•     Architectural Principles
•     Transactions
•     Building NServiceBus from Source files

• Samples
•     Web App Integration
•     Using NServiceBus with ASP MVC3
•     Encryption
•     Full Duplex - Request/Response
•     Generic Host - Logging
•     PubSub
•     Versioning
•     Message Mutators
•     Unobtrusive
•     Data Bus
•     Scale Out

• Day to Day
•     Dependency Injection
•     Support for child containers
•     Logging
•     Messages as Interfaces
•     Introducing IEvent and ICommand
•     Unobtrusive mode messages
•     Unit Testing
•     One way/Send only endpoints
•     Staying updated with NuGet
•     Scheduling with NServiceBus
• Hosting
•     In Your Process
•     NServiceBus Host
•     Profiles
•     More on Profiles
•     32-bit (x86) Host Process

• Management and Monitoring
•     Auditing
•     Monitoring
•     Msmq Information

• Scaling Out
•     Performance Information
•     Multi-Site with the Gateway
•     More about the Gateway
•     Multi-Server with the Distributor
•     Unit of work in NServiceBus V3
•     Unit Of Work implementation for RavenDB

• Publish-Subscribe
•     Overview
•     API and Configuration

• Long-Running Processes
•     Sagas

• Customization
•     Customizing Configuration
•     Pipeline Management Using Message Mutators

• Versioning
•     Migrating to NServiceBus 3.0 – Timeouts

Introducing IEvent and ICommand

One of the new features in NServiceBus v3 is the introduction of two new message interfaces, IEvent and ICommand. The purpose is to capture more of the intent of the messages that you as a user are defining. This will help NServiceBus to enforce messaging best practices and stop you from doing crazy things:)

Messages implementing ICommand

• Is not allowed to be published since all commands should have one logical owner and should be sent to the endpoint responsible for processing
• Can’t be subscribed and unsubscribed to
• Can’t implement IEvent

Messages implementing IEvent

• Can be published
• Can be subscribed and unsubscribed to
• Can’t be sent using Bus.Send() since all events should be Published
• Can’t implement ICommand
• Can’t be sent using the gateway, ie bus.SendToSites()

So please go ahead and use those additional interfaces if you wan’t NServiceBus to help you fall into the pit of success.

This article was written by Andreas Öhlund and the original blog post can be found here.