Is there a way to use NSB in a mixed environment (not all .NET) where the various parts of the system can share messages?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a way to use NSB in a mixed environment (not all .NET) where the various parts of the system can share messages?
There are a few options in this regard. First you can expose any NSB endpoint via WCF to allow non .NET components to get messages onto NSB. You may then return messages to the other components by also sending messages to a gateway endpoint that makes similar calls into the non .NET components via a .NET compatible API or service.
Secondly it is possible to write your own transport that could bridge over to another world. What I mean is that you could supply a JMS implementation that would run instead of MSMQ. You would still have to pick up the messages on your own on the other side.
Lastly we’ve seen people setup what is known as a Satellite in NSB to handle bridging to other systems via another ESB/Broker. A Satellite runs along side an endpoint with its own resources. You may consider setting up a full blown endpoint just to create this bridge.