What advice do you have for others considering Red Hat Fuse?

The maintenance required on my end, such as updates for example, is simple to use. The tool works well. The unique problem is the interface for creating the flows; that's one issue, but it's not a stopper. If the interface is complex to use, the quantity of developers who can work with it is very small. At that time, I was chief officer in middleware at an enterprise called VASS, where I had a team of around 25 persons, but only about two people had the capability to work in Red Hat Fuse, while the rest of the team was focused on middleware. I would rate this product eight out of ten overall.

I would rate Red Hat Fuse as eight out of ten. When the solution was being used in our organization, the JBoss or Red Hat support was great. The solution was highly stable, robust, and scalable, and our company availed itself of two or three years of extended support even after the product went into End-of-life. The product brings value to a company in terms of deployment, orchestration, scalability and robustness.

Red Hat Fuse is currently deployed on-premises in our organization. We have plans to move into the cloud as well. If you're looking for an enterprise service bus, Red Hat Fuse is one of the platforms on which you can reliably integrate. However, you need to take care of the usability part operationally. It will ensure that the business you ask for has every flexibility. Overall, I rate Red Hat Fuse an eight out of ten.

I would definitely recommend the solution to those planning to use it. If anyone is looking for an Enterprise Service Bus solution, then Red Hat Fuse is one of the options. Also, they do have various ESB solutions. Overall, I rate the solution an eight out of ten.

From my point of view, it's a very good option, especially if you are considering a flexible integration approach. It can be run on-premises or in the cloud, but running it in the cloud is the right choice, in my opinion. I would rate it a ten out of ten.

All nodes will be deployed on VMware and not on a cloud solution. Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the solution as nine out of ten. My advice is that the solution is geared toward developers and not a citizen designer. It's not for people who want to be able to do integrations using a low code environment.

I give the solution an eight out of ten. The solution is a Red Hat version of the Apache Camel which has been discontinued. The solution will be discontinued in 2024. There are already plans to move to a different product called Camel 3. There is not that much they can improve with the solution. They're just taking another Apache product and wrapping it up, and branding it as Red Hat, by giving the enterprise support for this version of the Open-Source product. Michael: From a version perspective, there is maintenance, When you need to move from one version to another. And this part, usually Red Hat is giving a good heads up and tries not to break compatibility as well. Unless they're changing the versions that are not compatible, of course, some features will not be compatible. But from an information perspective, they're giving a good heads-up and a good explanation.

I would give Red Hat Fuse a rating of seven out of ten.

As long as you are a Java developer, Red Hat Fuse is easier to learn than other integration solutions on the market. It's a Java framework first, making it quite easy to pick up and go. I would rate the product an eight out of 10 overall.

My company is using multiple versions of Red Hat Fuse for multiple customers. My company provides Red Hat Fuse services to customers. At least four or five customers use it. As for the maintenance of the solution, once it is in production, only one person is required to handle maintenance. It depends on the SLA, but Red Hat Fuse is not that maintenance-heavy. It doesn't require much maintenance. I'm recommending Red Hat Fuse to others because it's affordable and it's built on top of technology that is pretty popular and well supported. I'm rating Red Hat Fuse eight out of ten. It's resourceful, has a pretty decent performance, is built on popular technology, and it's very affordable. My company is both a customer and an integration partner of Red Hat Fuse.

If your integration needs are not that complex and you have plenty of time for your integration projects to go live, then you can go with this cheap ESB. It does everything that other ESBs do. On a scale of one to 10, where 10 is best, I would rate Red Hat Fuse as seven.

My advice for anybody who is considering Fuse is to research the market and talk to other customers. Try to make a good business case, express the expected benefits in figures, in money, as well as the costs. Try to have an honest, upfront negotiation with Red Hat, and try to estimate what will happen during the next few years. You want to understand the growth curve that might be involved and try to find use cases that are similar to yours because no two integrations are alike. Had we done this at the moment we chose Red Hat, we might have not changed our decision but we might have been more confident. Of course, we didn't have that evaluation done at that point in time. We have no regrets, but this is what I would suggest to a friend that asks me how to proceed in this case. Overall, this is a very good solution. The product quality is high. It's slightly complex upfront, but it's highly reliable. It has very good availability. It generates very few problems once you configure it properly. Of course, the configuration must be done carefully. As I mentioned, documentation could be improved and for small-scale implementations such as us, it works fine. I couldn't comment on large-scale implementations in the tens of thousands or hundreds of thousands of users because it's not what we have explored. Our implementations are smaller, but I could give a thumbs up to the solution, of course, considering its quality and what it delivers to cover our needs. In summary, this is a good product and other than our comments about the documentation and resource consumption, we are really satisfied. I would rate this solution a nine out of ten.

One of the things that we're planning to do is use Red Hat OpenShift for cloud availability because we want to take our platform to the cloud at some point in the future. We want to have more redundancy on the backend and doing so will also help us with high availability. Currently, we have almost 99.999%, but 100% is desired. My advice for anybody who is implementing Red Hat Fuse is to have an expert SME from outside of the organization, who has done the job. When you run into roadblocks such as bugs, you want to make sure that you have that support. If you compare other products from an open-source perspective, I would say Red Hat fits that bill. They have a lot of developers who contribute to the open-source community and it has helped us to stay on the cutting edge. It is beneficial to have open-source contributions to our solution. If the solution is not open-source then a company will lock itself into a vendor. That means that they will get locked into pricing that only the vendor can control, versus when you have a solution that is open-source, you can always go to other competitors. That's one very big advantage. Red Hat has good education packages and my developers can take advantage of that. We have a subscription for learning. Plus, when you have an open-source package, you are not bound by the vendors' learning resources. You can always research outside by going to the community and doing your own research. The advantage is that you are taking your questions and you are posting them out in the community and getting those answers. Sometimes, you are contributing to the community in the process. I feel that there is more knowledge, outside of the vendors, that gets restricted. If you want IBM, then you're just focused on IBM's community. When you are outside of that, you have a bigger open-source community that helps answer your questions. There's a definite advantage to having an open-source product. In summary, this is a great product that is scalable, stable, highly available, and has a good help desk. These are the reasons that Red Hat has been a very good solution for us and we have no complaints. I would rate this solution a nine out of ten.

My advice to somebody looking into this product would be: Be prepared to do a lot of reading. But the tool is quite flexible and quite powerful.

Actually, we are doing R&D on Red Hat Fuse. We are looking to move some of our application framework to use Red Hat Fuse. But we haven't decide yet. It's still in the decision stage. On a scale of one to ten, based on our earlier Proof of Concept, I would give Red Hat Fuse a seven. Because the Proof of Concept was done two years ago we are now going to resume again and we are now at the decision making point. We still find that we need some customization in order to meet our clients' needs. Even if it is more compliant, there are still some customizations required in order to meet our clients' requirements.

I would recommend Fuse. I don't think any other ESB tool makes big difference from Fuse. Many of this tools have the same problem: to publish and secure an internal service. Many tools bring other solutions to they ecosystems in order to extend to an API Gateway/Management functionality. You could reach the same adding others Red Hat tools.

I would recommend it to people because it is very good for starting with an ESB project. Depending on the size of the installation, it may not be necessary to use another tool. I would suggest starting with the documentation to see if it meets the requirements. I think that doing a proof of concept is a good idea because you will get a real perception of what the tool offers. Another thing that I suggest is to try and find the connector that you want to use and make sure that it is supported by Red Hat or another company. Overall, I think that this is a good tool. It is very versatile, although compared to other tools on the market, it doesn't have the appearance, or look and feel, of one that is very professional. You can do everything on the command line, but some people feel that it just doesn't look good. For me, agility and performance are more important than it being eye-catching. I would rate this solution an eight out of ten.

We are using the private cloud deployment model with Openshift as the provider. I would advise those considering implementation to play with the framework. If you try to understand the philosophy behind the framework it will make it easy to use. I would rate the solution ten out of ten.

In our case it was much easier to implement a new integration on that platform than on the previous platform we had. Furthermore, it's open source, it doesn't charge us anything. The other one was a quite an expensive platform you would use in custom development. We saved money and time. Honestly, it fulfills the needs we have at the moment.