The features I found most valuable in Red Hat Fuse are the OSB framework, containerization, and the integration of Apache technologies such as the NQ channel, CXF, etc. These are the features that are very prominent in the solution.
Red Hat Fuse also offers flexibility, so it's another valuable characteristic of the solution.
Because we have been doing Red Hat Fuse projects for three years, and over time we have matured, we can employ similar use cases and make use of accelerators or templates. It gives us an edge when we deliver these services or APIs quickly.
Systems Architect at a tech services company with 51-200 employees
Real User
2021-11-08T13:41:00Z
Nov 8, 2021
The most valuable part of Fuse is the fact that it's based on Red Hat Apache Camel. It is really good that it already comes with so many different connectors. That makes it relatively easy to use. We use their XML definition to define the routes, making it really easy to define the routing.
VP at a computer software company with 201-500 employees
Real User
2020-12-24T12:29:00Z
Dec 24, 2020
The installation is quite okay. We don't really change much in the configuration. Most of the time, most of the settings remain with the default and we are able to handle our needs using the default setting.
Business Solution Analyst at a manufacturing company with 10,001+ employees
Real User
2020-11-05T06:31:00Z
Nov 5, 2020
We usually had used PowerCenter for master data integration (by replication). But in some cases, it was better to use Fuse for providing the master data online. It doesn't make it necessary to replicate data.
Red Hat JBoss Fuse is a lightweight, flexible integration platform that enables rapid integration across the extended enterprise - on-premise or in the cloud. JBoss Fuse includes modular integration capabilities, an enterprise service bus (ESB), to unlock information.
The process workflow, where we can orchestrate and design the application by defining different routes, is really useful.
With a premium, one can get support 24 hours.
I would rate the scalability a ten out of ten. We are an enterprise business.
The initial setup process is quite straightforward.
It's very lightweight. There's no need for any specialized tools in order to deploy any service for Red Hat Fuse.
The most valuable feature is that it's the same as Apache Camel.
Red Hat Fuse's best features are that it's very easy to set up and maintain.
The solution has more tooling and options.
The features I found most valuable in Red Hat Fuse are the OSB framework, containerization, and the integration of Apache technologies such as the NQ channel, CXF, etc. These are the features that are very prominent in the solution.
Red Hat Fuse also offers flexibility, so it's another valuable characteristic of the solution.
Because we have been doing Red Hat Fuse projects for three years, and over time we have matured, we can employ similar use cases and make use of accelerators or templates. It gives us an edge when we deliver these services or APIs quickly.
More than a feature, I would say that the reliability of the platform is the most valuable aspect.
This solution's adaptability to our use case has helped us integrate our systems seamlessly.
The most valuable part of Fuse is the fact that it's based on Red Hat Apache Camel. It is really good that it already comes with so many different connectors. That makes it relatively easy to use. We use their XML definition to define the routes, making it really easy to define the routing.
The installation is quite okay. We don't really change much in the configuration. Most of the time, most of the settings remain with the default and we are able to handle our needs using the default setting.
We usually had used PowerCenter for master data integration (by replication). But in some cases, it was better to use Fuse for providing the master data online. It doesn't make it necessary to replicate data.
The most valuable feature is the software development environment.
The solution is stable. We have gone for months or years without any issue. There are no memory restarts, so from my point of view, it's very stable.
I found it was quite easy to set up and implement.