Essentially FUSE ESB is our release of Apache ServiceMix. This includes a Camel component. With FUSE ESB we version the Camel component based on the FUSE Mediation Router. This means you can be sure that the versions of FUSE ESB\ServiceMix and FUSE Mediation Router\Camel have been fully tested with each other.
You are probably referring to the fact that ServiceMix includes an EIP component that does a lot of the routing that camel does. It also includes transport components that are included in Camel. These features in Camel allows you to run a standalone pure routing engine. Note that Camel is not a container. If you deploy your Camel route into ServiceMix you can take advantage of lifecycling, versioning, administration and deployments. You can choose the JBI and/or OSGi container features in ServiceMix to achieve this.
Hope that helps,
Thanks for your valuable piece of information.Yes, you have understood my question correctly.
As architect/developer I would be confused whether i need to use fuse esb to create integration flows or to use fuse mediation router?
As i see in your FID enviorment seems to focus more on fuse mediation router than on fuse esb.The eip diagrams and other flows are more fuse mediation router centric.
So is it best practice to create flows on fuse mediation router and use service mix for deployment purpose?
Thanks for the links, Now things are much clearer.