3 Replies Latest reply on Oct 18, 2009 10:19 PM by Brian Taylor

    FUSE ESB vs. FUSE Mediation Router

    Torsten Mielke Apprentice

      Hello,

       

      Could we please get some discussion started on how the FUSE ESB compares to the FUSE Mediation Router? In which scenarios does each of the products show its strengths? Is there an overlap in functionality? How do I decide which product is better suited for my integration project?

       

      A provoking question: Is it fair to say  Spring + Fuse Mediation Router = Fuse ESB without JBI standard?

        • 1. Re: FUSE ESB vs. FUSE Mediation Router
          James Strachan Newbie

          Here is an FAQ entry that tries to cover this point. In essence the FUSE Mediation Router is an integration framework that can be used stand alone or inside the FUSE ESB. When it is inside the FUSE ESB it can route message exchanges on the JBI bus using the JBI endpoint notation. Its best to think of the FUSE Mediation Router as kinda like an alternative to the servicemix-eip component which works both inside and outside of a JBI container.

           

          You can create a JBI endpoint in a Camel route as follows...

           

          from("jbi:service:http://foo.bar.org/MyService").to(anyCamelEndpointUri);
          

           

          Or you can route any Camel endpoint to a JBI compont as follows

           

          from(anyCamelEndpoint).to("jbi:service:http://foo.bar.org/MyService");
          

           

          Edited by: jstrachan on Dec 5, 2007 10:08 AM

          • 2. Re: FUSE ESB vs. FUSE Mediation Router
            Bruce Snyder Novice

             

            Could we please get some discussion started on how the FUSE ESB compares to the FUSE Mediation Router? In which scenarios does each of the products show its strengths? Is there an overlap in functionality? How do I decide which product is better suited for my integration project?

             

             

            There is definitely some overlap in functionality. This is because we began to implement the EIP patterns in the servicemix-eip prior to the creation of Camel. As the work on the EIP patterns progressed in the ServiceMix project, we came to discover that we should make them more widely available outside of ServiceMix. So Camel was created for this purpose and it is not tied to ServiceMix but can be used inside of ServiceMix.

             

            Moving forward, if you're using ServiceMix, my advice is to use the Camel components for routing via the EIP patterns instead of the servicemix-eip component. This allows you to deploy your routes in ServiceMix using the servicemix-camel component as well as to deploy them stand alone in Camel as well.

             

             

            A provoking question: Is it fair to say Spring + Fuse Mediation Router = Fuse ESB without JBI standard?

             

             

            To a certain degree, this is true at a high level. But beyond the JBI standard, however, ServiceMix provides many other features.

             

            Bruce

            • 3. Re: FUSE ESB vs. FUSE Mediation Router
              Brian Taylor Newbie

              Please provide a use case that would be best implemented with Fuse ESB over the Mediation Router. The above mentioned FAQ isn't doing it for me.

               

              Edited by: bktaylor7 on Oct 19, 2009 2:18 AM