Versions

Roadmap

The primary goals were, are, and will continue to be

Stability, Flexibility, and Ease of Use.

Robust under failure conditions when running.
Pluggable for replacing any underlying technology.
Simplicity in development, fluidly moving to production.

More of all three on the road ahead.

Have a feature you just wish came out of the box? Tell us!

Next Version: 3.0

Main Capabilities:

1. Azure integration
2. Improved timeout management
3. Improved pluggability

Azure integration brings certain challenges with it in that Azure Queues don't support transactions - there is no Distributed Transaction Coordinator in the cloud.

Improvements to the durable timeout management will enable a single process to manage multiple timeout scales - from minutes to months. Upgrading to a newer version of TopShelf falls under this capability which will enable a simpler deployment footprint, no longer requiring a separate process for each queue. Instead, a single process will manage multiple AppDomains, each working against its own queue.

Improvements to pluggability will change how NHibernate gets integrated, simplifying matters for developers who want to use a different version of NHibernate than that which comes with NServiceBus. On top of that, developers will have access to the incoming and outgoing message pipelines giving much more control over how messages move from memory to wire and back.

On top of these 3 main capabilities, improving developer productivity and shortening the learning curve remain primary directives for the future development of NServiceBus. In practical terms, this means introducing more conventions and reducing the amount of configuration needed.