support amqp.org open protocol cross-platform implementation like rabbitmq or qpid etc
I don't like building new solutions on top of closed-source proprietary implementations and protocols. I noticed that amqp or any of the implementations are not on the todo list when I think it should be at the very top. Pub/Sub messaging is best left up to the broker/infrastructure. It would also nServiceBus a lot of value if it could be run completely on *nix os's.
We’re in the final phases of getting our ActiveMQ transport done.
The RabbitMQ transport is just about done. We're going to be opening it up for a public beta in the next week or two.
John Coxhead commented
Any update on plans to release RabbitMQ integration
We're going to be putting in some voodoo to deduplicate messages as a part of version 4.0 that will then allow us to give a bullet-proof RabbitMQ implementation.
Expect that around Q1 2013.
mick delaney commented
will that also support other amqp compatible solutions, e.g. rabbitmq ?
obviously with the caveat that distributed tx is not available etc.
What we're looking at doing is integrating with ActiveMQ via one of our gateway channels.
This will provide interoperability but won't enable running NServiceBus on non-.NET platforms (yet).
salvatore iacono commented
when will you release version 2.1? We are interested in using RabbitMQ.
After talking with the guys at RabbitMQ, it turns out that they don't support distributed transactions, and neither is it a part of the amqp spec. This is a core part of how NServiceBus works which will make it more difficult to implement.
alexis richardson commented
Guys, does this help?
Kristoffer Sheather commented
How is this feature coming along? I'm quite interested in using AMQP (RabbitMQ specifically) for our message bus transport, in preference to the closed MSMQ technology.