One of the features I found most valuable in Red Hat Fuse is that it has a lot of containers so you won't have to worry about load balancing. In the past, there was a cut-off, but nowadays, Red Hat Fuse is moving off of that, so my team is utilizing it the most for load balancing, particularly running goal applications and three to five containers. There's automatic load balancing so you won't have to worry too much.

I also found that component-wise, you don't have to do much coding in Red Hat Fuse because everything is configurable, for example, XML-based coding. Coding isn't that difficult.

Performance-wise, I also found the solution to be quite good and its processing is quite fast. My team is processing a huge amount of data with the help of Red Hat Fuse.

What I like about Red Hat Fuse is that it's a well-established integration software. I find all aspects of the tool positive.

Fuse has a lot of capabilities that we use.

There is an open-source package within Fuse called Camel, which allows you to build interface routes with a programming language using Camel extensions. We use Java as our coding language and there are open-source integration patterns included. Fuse makes the integration much easier to do.

This product is adaptable and scalable because of the DevOps features. In our environment, DevOps made it easy to adapt and we were able to customize a lot of things for our use case.

Red Hat Fuse is an ESB. The most important feature of any ESB is its connectivity to diverse systems or endpoints. This is one of the key features that every ESB provides. 

We can expose APIs and consume them.

Red Hat Fuse incorporates all the latest ESB features.

The process workflow, where we can orchestrate and design the application by defining different routes, is really useful.

Like any other ESBs, Red Hat Fuse is one of the ESBs, and it particularly comes as a part of a suite of OCP in OpenShift. The entire security can range from containerization and the parts which have been built into the solution.

Feature-wise, it was easy to integrate with cloud platforms, especially other cloud platforms which are already available. Also, features like containerization are there in the solution. So, it is not necessary to go with the trend since Red Hat Fuse has already provided us with an option where if you don't want a container, you can have it as a stand-alone, or if you want a container, you can do it container-wise. So there were multiple things that we could correlate, and then we were okay going ahead with the solution.

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.

The most valuable feature is that it's the same as Apache Camel. 

Red Hat Fuse is a Red Hat version of an Open-Source platform called the Budget Camel.

It was pretty effective in aligning the software. We also like containerization capabilities. We're interested in how this container technology will develop. We're interested in the cloud and how it will develop. We're integrating a lot of things towards that end and Red Hat is helping us effectively move that way. It's opening up the prospect for more capabilities. 

The stability has been good.

The solution can scale. 

More than a feature, I would say that the reliability of the platform is the most valuable aspect. We have several servers and it is highly resilient, it is always available, and it requires very little maintenance. Of course, when something doesn't work, it's highly complicated. Because of the nature of the applications that we interface with, the product is highly complex but it's highly reliable as well. This is why we keep using it.

The AMQ strings are the most valuable. Also, it's Apache Camel compliant. There are a lot of components, but one component, in particular, stands out.

Red Hat Fuse is developer friendly. The solution has more tooling and options. Because it is based on existing platforms, it is easy to implement, as you don't need to relearn everything. It is everything I want from a full integration solution.

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.

Because Apache Camel is widely used, it was quite easy to find examples for use cases that are similar to ours. We were able to get it set up and do a proof of concept quite easily, without relying on the external consultants too much. The fact that we could download it with the developer license and set up a test environment and try things out, before we committed to purchasing an actual subscription, was also very helpful in getting us set up quickly. 

It's very lightweight. There's no need for any specialized tools in order to deploy any service for Red Hat Fuse.

Overall, it is a very, very good platform.

The support training that comes with the product is amazing. 

There are a lot of engineers that know the platform. In Argentina, it's very popular.

It offers a very simple setup.

The capabilities it has to integrate and communicate with other systems are impressive.

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. So any application, especially new developments, get master data from a centralized repository (through Fuse), instead of having the master data replicated.

The most valuable feature for us is the close connection with Camel because we already used it. That's really why we chose Red Hat Fuse.

Red Hat Fuse's best features are that it's very easy to set up and maintain.

When comparing the database in Red Hat to that in Windows, we do prefer Red Hat based on its performance.

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. But for some clients, maybe due to their connection, or due to their OEM, we need to adjust the settings a bit. 

So far there is not much concern.

The solution offers competent modules that help you to integrate with other platforms and it allows you to write applications in a few lines of code.

The most valuable feature is the software development environment.