Red Hat Fuse Reviews

Our company used Red Hat Fuse to integrate layers of numerous applications. The solution has also been used in our organization for orchestration purposes of multiple microservices over the years. In our company, we had fuse bundles and interactive domains, and the fuse was the common source where all the abstracted layers and vendor details could be viewed. 

One of the best features of Red Hat Fuse is that one single console is provided for all the applications. The routing system of the product supports Camel routing, which allows programmers to write minimal code. Red Hat Fuse is a good product for developers, deployment teams, and support teams. It's very easy to build a new environment using Red Hat Fuse because most of the processes are already automated using the fuse. 

Presently at our company, we are not giving much value to Red Hat Fuse because better tools have launched in the market. New additional features have arrived in the solution for JBoss integration. 

Regarding use cases, the solution is not for internal consumption. It is used for our customers. The solution is an Enterprise Service Bus or ESB.

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.

We have a couple of different interfaces through SOAP, REST, FILE, and Kafka. We receive different inputs from the external interfaces, transform them, and do some kind of enrichment. Finally, we use the routing to publish to downward streams.

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

We are using Red Hat Fuse for integration purposes, in particular, we are using it as an integration layer. It's for connecting through various adopters, for example, web service consumptions and other file-based interactions. Red Hat Fuse gives a lot of capabilities for various integration points. We are using Camel, then along with that solution, we are using Red Hat Fuse for all integrations, mainly for file-based and web-service based interactions, as this is how our projects were designed.

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.

Red Hat Fuse is used for communicating and interfacing between systems. It's used for system integration and it's also used for messaging.

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

Mostly it's combined with API management. It is for API management switches as well as the USB portions. We are using mostly email-based USB portion but we are hosting our API so in terms of exposing the API, it had been used for API management. 

The key portion, for now, is mostly under API management software. It's for the publishing of APIs then pulling the security.

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. 

We use it because it is easy to integrate with any other application, and when we tried to do an upgrade, it was really easy for us to do that. Plus, it is compatible with other programming languages. Then, to learn and to upgrade ourselves to this platform was easy to train people who were working with us on this platform was not something new or out of the box kind of a thing. It was something people were familiar with, so that is the reason. That is one of the reasons for choosing it. Additionally, we are getting support, specifically continuous support, which is always there for us.

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 primary use case of this solution is to implement our microservices and refactor our monolith products. Not the environment, but libraries that you can build pretty sophisticated workflows

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.