Is NServiceBus a good fit for cross platform integration?

Is NServiceBus a good fit if you want to integrate .NET开发者_如何转开发 applications with other applications written in languages like python or even php on Linux?

Of course you would have to replace MSMQ with another queuing solution like ActiveMQ or RabbitMQ. I already read that this is possible. But is it actually feasible and stable?

Besides that, how much magic does NServiceBus implement for basic scenarios like pub/sub with durable subscriptions, which you would have to re-implement in the other languages.

If NServiceBus is not a good fit, what would you recommend instead?

---

Alebo, I believe NServiceBus is a good fit for connecting components from other platforms. We create "adapters" that bridge the c#-centric bus with other technologies. We've got one that takes command as SOAP calls, another that looks for files in a directory, another that accepts POP3. Then, we simply put those messages on the bus. We do the same thing with published events going the other direction. The messages are just XML files that any language can create and consume.

It works great, and we didn't have to change out the MSMQ provider.