JBoss ESB vs Red Hat Fuse comparison

"The solution is very easy to use. I can download the trial version and just give it a go."

"The solution has more tooling and options."

"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 process workflow, where we can orchestrate and design the application by defining different routes, is really useful."

"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."

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

"The most valuable feature is the software development environment."

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

"The stability has been good."

"The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems."

"As its learning curve is quite steep, developer dependency will always be there in the case of a Red Hat Fuse development. This should be improved for developers. There should be some built-in connectors so the grind of the developer can be reduced."

"In the next release, I'd like more stability and more security overall."

"Red Hat Fuse doesn't have a lot of administrative control like other applications."

"The pricing model could be adjusted. The price should be lower."

"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."

"While it's a good platform, the pricing is a bit high."

"Our clients would like to see the user interface improved so that it is more user-friendly."

"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."

"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."

"This is an open-source product that can be used free of charge."

"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."

"The solution doesn't have independent licensing."

"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."

"Our license for Red Hat Fuse is around $27,000 per year, which is very expensive."

"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."