This document summarizes the new features in NServiceBus 3.0, including improved out-of-the-box experience, naming conventions, handling timeouts, bridging remote sites, and other random features. Key points include default storage bundled with NServiceBus, conventions based on endpoint names, a new timeout manager for managing timeouts at each endpoint, and using gateways to bridge communication between physical sites. The document concludes with a Q&A section.
9. Conventions based on the
endpoint name
Database Orders
Input queue Orders
Orders
Timeouts Orders.Timeouts
Bus.dll
Gateway url http://localhost/orders
10. Naming endpoints
• Defaults to your namespace
• Attribute: [EndpointName(“Orders”)]
• Install: /serviceName:Orders
• Configure.DefineEndpointName(…)
14. Bending time to your will
• Sagas
– RequestUtcTimeout<T>(…)
– IHandleTimeout<T>
– v2.6 Timeouts still supported
• Bus.Defer<T>(…)
• All endpoints have a local
timeoutmanager
18. What can the gateway do
for you?
• Bridge physical sites
• Supports multiple channels
• Does de-duplication
• Performs retries
• Can act as a alternate channel for
administrative messages
• Enable Browser NServiceBus
communications
21. Data bus
File share / Blob storage
Data Bus
App Main transport App
Bus.dll Bus.dll
MSMQ / Azure Queues
public DataBusProperty<byte[]> Image{ get; set; }
22. Other features
• Unobtrusive mode
• DatabusProperty<T>
• ISendMessages / IReceiveMessages
• Modeling tools
• Exception details attached to messages
in the error queue
• Client side pipeline
