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.

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. 

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.

We use Red Hat Fuse in conjunction with ActiveMQ as our healthcare integration platform. Our electronic medical records (EMR) system is called Epic, and we have to send information from it to all of our ancillary systems. The process is that we take the data coming from Epic and we send it to the downstream apps, for example, to the radiology lab. As an overview, it can be thought of as a hub and spoke model.

The EMR sits in the middle, like the center of the universe. We have the Fuse interface and we also have APIM, both of which take information that is coming from EMR. Surrounding these are approximately 140 applications, all receiving data from these systems. We categorize these as lab, radiology, pharmacy, and materials management.

A lot of these apps need demographic information. For instance, a patient logs into the system and needs a demographics update. This is one of the purposes that the system serves.

It's a well-integrated platform and without the Fuse interface engine, Epic cannot talk to the downstream, ancillary systems.

This solution's adaptability to our use case has helped us integrate our systems seamlessly.

Functionality-wise, the workflow has become more automated. When something is ordered within electronic medical records, it's easily available in the ancillary systems. When the results are in the ancillary systems, they can appear in electronic medical systems. It's one integrated system.

From a workflow perspective, it's very quick and efficient. Doctors and physicians can see their notes, documents, and all of the information they need. The interface engine sitting in the middle makes that possible.

I am an Integration Consultant. At my company, we are using Red Hat Fuse as our integration suite so we can connect all of our different software components.

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.

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.