Red Hat / JBoss products for integration / mediation

[mranest]

Hello,

I've been monitoring Fuse 6.1 beta builds for some time now, and to my understanding the product has built sufficient momentum inside Red Hat (e.g. Openshift integration). At the same time though there are the old legacy ESB offerings of Red Hat / JBoss (JBossESB, SOA platform), with one new project (SwitchYard) claiming to be the building block of the next version of SOA platform. Moreover there are additional offerings in the BPMN space, with existing or announced integrations with one or more of the above-mentioned tools.

My question is: what should we expect in the future for Fuse, and how will it compete with/augment the rest of integration/mediation tools that Red Hat offers?

Kind regards,

Anestis

[davsclaus]

There are 2 fuse products going forward

These 2 products is middleware

- Red Hat JBoss Fuse

- Red Hat JBoss Fuse Service Works

And this related product is the ActiveMQ message broker

- Red Hat JBoss A-MQ

[davsclaus]

The older products JBossESB / SOA Platform, has been replaced with the new Red Hat JBoss Fuse Service Works product.

eg Red Hat started the SwitchYard project many years ago as a new foundation for their next generation ESB. And this is today the JBoss Fuse Service Works product.

The JBoss Fuse product is based on Red Hat acquired FuseSource which had a product named Fuse ESB.

And for JBoss Fuse there is a community project as well called fabric8

http://fabric8.io/

[mranest]

Claus,

thank you very much for both answers. Am I right to assume that the middleware of choice for deploying Camel routes will be JBoss Fuse, at least for the foreseeable future?

Kind regards,

Anestis

[alansantos]

Anestis,

I'd like to just expand a bit on Claus' answer.   You can consider Fuse part of the Red Hat integration product family. We have three products in that family that are built on each other, adding capabilities for different use-cases.  Briefly, there's

     1) A-MQ which allows integration via messaging;

     2) Fuse which includes A-MQ and offers integration capabilities you'd expect in a service bus - connectivity, mediation, transformation, etc.

     3) Fuse Service Works which includes Fuse and offers governance and other technologies you'd expect platform in more traditional integration platforms - A repository; Business Transaction Monitoring; BPEL, BPMN2 & Business Rules to support orchestration and decision management; An SCA like runtime library with developer tooling; and finally it also includes a subscription to EAP, letting you decide whether you want to run all of this in Karaf or EAP. 

There's a temporary caveat here - some of FSW hasn't yet been ported over to Karaf from EAP.  The 6.1 release of FSW and A-MQ will address this.

As to your question "Am I right to assume that the middleware of choice for deploying Camel routes will be JBoss Fuse, at least for the foreseeable future?" - the answer is yes and you can do that with either Fuse or Fuse Service works depending upon what else you want to do.

You'll definitely be able to do this well into the foreseeable future, we have big plans for Camel and other Fuse technologies (e.g. Fabric8) and you'll see those being used more and more within Red Hat middleware. 

Hope this helps.