Red Hat integrate FuseSource ESB and messaging technologies into JBoss stack
The open source giant reveal JBoss Fuse and JBoss A-MQ in a change to their middleware stack.
Since the acquisition of Fusesource last year, Red Hat
have been decidedly quiet on how the integration and messaging
technologies would fit into their plans. The covers came off today
however, with the assimilation of JBoss Fuse and JBoss A-MQ into
their middleware division.
Red Hat has rebranded Fusesource’s enterprise service bus (ESB), Fuse and their Advance Messaging Queuing (AMQ) protocol and integrated the duo into their stack.
JBoss Fuse is based on Apache Camel, the open source integration framework which Fusesource offered training and enterprise support for. While JBoss already produce their own ESB for larger application servers, JBoss Fuse will act as a lightweight alternative running on the OSGI-based Apache Karaf container, according to Pierre Fricke, director of product line management for Red Hat’s JBoss SOA platforms.
However, JBoss A-MQ, formerly known as Fuse Message Broker, will eventually replace Red Hat’s MRG messaging protocol. Those using MRG need not worry however – Red Hat will continue to support the protocol, before phasing it out in the next few years.
“JBoss A-MQ will become our main messaging platform going forward,” Fricke told the IDG News Service. It’s a logical choice to back the standard’s–based Apache ActiveMQ project, which already has a large community behind it.
It was only a matter of time before the open source giant
revealed how they would use Fusesource’s technologies, and it’s
clear that they regard both highly in renewing their middleware
Betas for both products will become available this week, before a general release in April. Red Hat say they will incorporate both into JBoss Developer Studio, the Eclipse-based tooling project, as well as the JBoss Operations Network, which focuses on admin management software.