Try our new research platform with insights from 80,000+ expert users

OpenESB vs Red Hat Fuse comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

OpenESB
Ranking in Enterprise Service Bus (ESB)
14th
Average Rating
8.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
Red Hat Fuse
Ranking in Enterprise Service Bus (ESB)
4th
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
23
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Enterprise Service Bus (ESB) category, the mindshare of OpenESB is 1.4%, down from 1.8% compared to the previous year. The mindshare of Red Hat Fuse is 8.8%, down from 10.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Service Bus (ESB)
 

Featured Reviews

PP
Enables us to define the business process and integrate it with other software
I used to work with Integration Bus. What is interesting is that the two products were made mainly by the same team, but OpenESB is lighter, you can run it on a simple GBM. It's lighter and has quite a few resources, no application server, and no database. This provides you with more intelligence because there is some kind of friction in the routing service, and you can play with that friction to provide some connection policy, like the last deployed policy. For example, if you were to install version one, and afterward, you deployed version two, automatically — if you decided that your connection will be the right deployed connection — you would be routed to the last version. If it doesn't work, you would just need to redeploy version one. Also, there are higher-level concepts, such as the interface of services, which allows you to define your interface and choose the method of implementation, like Java for example. On the other hand, with OpenESB, I am more connected. At the monitoring level, you can trust the level and replay the process, which is interesting, but because you have to store everything on the database, you have a conventional system that makes your system require more resources. The push ability to extract data from the process and then publish it in the data container is very interesting. For example, by using a database like Google's big data analytic search, you can create your own analytics from the data in your process without disturbing the process.
Kaushal  Kedia - PeerSpot reviewer
Configurable, doesn't require much coding, and has an automatic load balancing feature, but its development features need improvement
What needs to be improved in Red Hat Fuse is on the development side because when you use it for development purposes, it lacks a user interface compared to what MuleSoft has, so it's a bit difficult for users. There are good and bad points in Red Hat Fuse, but mostly the solution has good points. There's also another similar product in the market: IB Information Builder which is a product that has recently been taken over by TIBCO, and TIBCO has a similar integration product. It's similar to MuleSoft because both TIBCO and MuleSoft have user interfaces on the development side, so if I have to define a route where one particular flow should follow a particular way, for example, service should be consumed from this point, and these are my source and target, I'd be able to do those on MuleSoft and TIBCO more easily, but not in Red Hat Fuse. The development features of Red Hat Fuse need improvement, but I feel the team has done a lot in the latest version, and now Red Hat Fuse will be removed from the market and the focus will be on OpenShift purely. There is also a new product called Red Hat Integration and there will be a movement towards Docker because a major drawback of Red Hat Fuse is that it doesn't have small containers, so every time, you'll need dedicated virtual machines on top of those you're running, but now, it seems Kubernetes will be used. In the past, in the older version of Red Hat Fuse, you have a full container and the whole application is deployed on containers one, two, and three, so you don't have the option of splitting. It's similar to microservices, but now those things are taken care of in the latest version, and the older version of Red Hat Fuse will come to an end. An additional feature I'd like to see in Red Hat Fuse is a direct integration, particularly with CI/CD, which can help reduce overhead because you won't need to have a big DevOps team for building, preparation, and deployment. Dockers and microservices support are also additional features I'd like to see in the solution. More successful deployments will also help make Red Hat Fuse better.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The process-oriented solution allows you to define choreography and orchestration."
"OpenESB pushes the organization to clearly define service boundaries and interfaces. So it motives the business and the development teams to clearly define their business services and processes they want to implement. OpenESB supports fine and coarse-grain granularity for the services and supports top-down and bottom-up approaches for the services, processes definition, and composition."
"The core is very stable."
"One of the most valuable features is being able to implement business processes while keeping track of the design from BPMN to a BPEL Implementation."
"I found it was quite easy to set up and implement."
"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."
"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."
"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."
"Red Hat Fuse's best features are that it's very easy to set up and maintain."
"What I like about Red Hat Fuse is that it's a well-established integration software. I find all aspects of the tool positive."
"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."
 

Cons

"The documentation needs to be better."
"Cloud deployment is weak and needs to be improved."
"Regarding its management, a web console being able to synchronize distributed instances would be great."
"The documentation of the product must be improved. It could be tricky to find the right documentation on a topic since the documentation is spread in many places. I advise the new joiner to contact the community to get entry points and additional documentation. Tutorial and Video must be present to take up the product."
"The web tools need to be updated."
"For improvement, they can consider the way we collaborate with other applications...Right now, in Red Hat Fuse, everything is not available under one umbrella."
"There is definitely a bit of a learning curve."
"In the next release, I'd like more stability and more security overall."
"It might help if, in the documentation, there were a comments section or some kind of community input. I might read a page of documentation and not fully understand everything, or it might not quite answer the question I had. If there were a section associated with it where people could discuss the same topic, that might be helpful because somebody else might have already asked the question that I had."
"My company doesn't have any experience with other messaging tools, so it's difficult to mention what areas could be improved in Red Hat Fuse, but it could be pricing because I find it expensive."
"The stability of the solution is an area with a shortcoming that needs to be improved."
"While it's a good platform, the pricing is a bit high."
 

Pricing and Cost Advice

"The Community Edition is a full product you can use in production, it does not have limitations like other alternatives."
"The cost for the prediction instrument is high because it is charged per instances based on prediction, but the rest of the solution is free."
"There are two versions. The first is the community version, which is free and contains the last part of the feature, but if you want to get the Enterprise version, you'll have to pay €60,000 which covers support and two instances on production."
"In terms of pricing, Red Hat Fuse is a bit expensive because nowadays, if I'm just comparing it with OpenShift with Kubernetes, so Kubernetes and OpenShift, are similar, and Kubernetes is open source, so Red Hat Fuse is quite expensive in terms of support, but Red Hat Fuse provides value for money because it provides good support. If you want to get something, you need to pay for it."
"The most important feature of Fuse is the cost. It is open source and a cheap option for an ESB. So, most of the clients in the Middle East and Asian countries prefer this ESB. Other ESBs, like MuleSoft and IBM API Connect, are pretty expensive. Because it is open source, Red Hat Fuse is the cheapest solution, providing almost every integration capability."
"Pricing has been something that we have been working with Red Hat on, year over year. We have preferred pricing with the university because we are involved in education and research."
"The solution doesn't have independent licensing."
"This is an expensive product. It costs a lot and although it's worth the money, the explanations that we need to give to our top executives are highly complicated."
"After doing some Googling and comparisons, the main standouts were MuleSoft and Red Hat Fuse. One of the big factors in our decision to go with Fuse was the licensing cost. It was cheaper to go with Fuse."
"We are paying around $24 million across five years."
"My company pays for the license of Red Hat Fuse yearly. At the end of the day, it's a low-cost solution, and its support licenses are still very decently priced versus bigger operators such as IBM, etc. Red Hat Fuse is much more affordable than other solutions. On a scale of one to five, with one being cheap and five being extremely expensive, I'm rating its pricing a one."
report
Use our free recommendation engine to learn which Enterprise Service Bus (ESB) solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
16%
Wellness & Fitness Company
10%
Manufacturing Company
6%
Financial Services Firm
20%
Computer Software Company
18%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Red Hat Fuse?
The process workflow, where we can orchestrate and design the application by defining different routes, is really useful.
What is your experience regarding pricing and costs for Red Hat Fuse?
You need to pay for the license. It's not free. I'm not aware of the exact prices. There are no extra costs in addition to the standard licensing since it is a subscription-based solution.
What needs improvement with Red Hat Fuse?
I haven't experienced the online part of Red Hat Fuse. Red Hat Fuse doesn't have a lot of administrative control like other applications. Using administrative control, the operational user can view...
 

Comparisons

 

Also Known As

No data available
Fuse ESB, FuseSource
 

Learn More

Video not available
 

Overview

 

Sample Customers

Information Not Available
Avianca, American Product Distributors (APD), Kings College Hospital, AMD, CenturyLink, AECOM, E*TRADE
Find out what your peers are saying about OpenESB vs. Red Hat Fuse and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.