The initial setup for Red Hat Fuse was difficult. It was a bit complex and it was not as smooth as the initial setup for OpenShift which was very straightforward. On a scale of one to five, with one being the worst and five being the best, my rating for the initial setup, integration, and deployment of Red Hat Fuse is three out of five.

I found Red Hat Fuse easy to set up. I'm rating its setup a four out of five.

The initial setup was not straightforward, because of the dependencies that it needed and all of the things that we wanted to do with it. We as a team were learning the product, and we had contractors to assist us.

Once it was set up, learning the product took approximately six months. Adapting it and customizing it to our solution was complete within six months and then we started implementing the product.

The initial setup is of medium complexity. However, compared to MuleSoft, it is the most straightforward thing. You need to do minimal installations. You just need to set up Java on your system and install Anypoint Studio to work on. 

In the case of Red Hat Fuse, you need to also ensure that you have Java installed and will need to install CodeReady Studio. There might be some dependency issues, which you will need to resolve. That is why it is of medium complexity to set up. 

Red Hat Fuse deployments are time-consuming, because of the learning curve.

If you are not implementing CI/CD, the deployment time will be minimal. If you use hot deployment methods, you can copy your JAR file or WAR file to the on-premises' host folder, then it will deploy immediately. Or, you could use some CI/CD stuff for deploying them, where you are running tests and using pipelines to check in from the source control management systems, but that will take some time. 

The deployment time does not matter. Every other tool is basically built on Java. In the end, all the deployables are running on a JAR or JVM. So, the time is the same for every other ESB.

Compared to other ESBs, the delivery time will not be faster. The delivery time will be more in the case of Fuse, depending on the use case. With a complex use case, you need to do more custom development for Fuse. It is a give-and-take scenario because it is the cheapest ESB available in the market. 

Red Hat Fuse’s initial setup is easy.

The initial setup is not very complex. It is a bit com, but not very complex.

The time for deployment depends upon the availability of the various environments or infrastructures. You can set it up in a day.

Since the setup process is UI based, there is nothing much. The setup process is UI based, and there is nothing much involved in the setup process, owing to which it can just be improved.

The solution can be deployed on-premises and on a cloud.

For the deployments and maintenance, we need around six technically sound people. It is not such that any layman can operate the solution.

When I say deployment process, like, initially, we were using OCP directly to, like, finish when we do any development work on a local, we put the service on to JAR file, and after having it packed into a JAR file, and then on to an OCP platform, we upgrade since there is also an option with Red Hat Fuse which allows you to combine it to the cloud platform like Azure. So, we did that with Azure, Red Hat, and OCP, and now we have got CI/CD. So, all you need to do is, like, buttons. You don't even need to get into the server and look into the health. Everything is lined up for you. You can easily have it on one board. So that's how it has helped. I'm not sure if Red Hat has any CI/CD platform, while currently, Azure has it, like a board system, and onto it you can have Agile, like, to create where the team can create the task and all, like a Kanban board. And each task can be assigned to pull any activity you are doing. If you are deploying anything, you can simply map it to the task assigned. So, not everybody is technical in the team, but people do understand terminologies, so if a developer is doing any deployment work, at least he can inform the whole team what has happened. They don't need to know the nitty-gritty of how it is happening. Also, you don't need to drop an email or tell anyone personally that, yes, I have done it. It is already there on both, like, to set one place, you don't need to write down anything to anyone.

The initial setup for Red Hat Fuse was a little bit complex, especially when compared with Spring Boot. Though there was a little bit of complexity involved during the setup of Red Hat Fuse, it was still manageable. The setup for the solution was okay.

The solution is a Java package so there is no setup.

The initial setup can be complex, especially, if, like us, a company is trying to learn and understand the system. We ended up getting outside assistance. 

The deployment is taking longer than anticipated. We had planned it to be nine months and we've had a lot of delays in the project start. We're kind of disappointed it's now 2022 and the solution was appointed at the end of 2020. It's been a year and four months or so of implementing it.  

This initial setup is complex. The installation and implementation for the first integration, and perhaps most applications and projects that you can think of, is complex. The first time, it takes longer because you don't have the experience. It's more difficult. Then, you get used to it and you know the inner workings of the tool. You learn to know what might show up at a certain time and place, but for the first implementation, it's complex overall.

The first project took slightly less than one year to implement, perhaps between nine and ten months. In that case, the project required completing the installation, as well as the creation of the first integration.

From my point of view, the installation of Red Hat Fuse is relatively easy. You just need to open OpenShift Operators and install it. It's easy to install.

We have it on the cloud. OpenShift is considered a cloud product, although we have it installed in our own data centers. It's like a private cloud.

The initial setup is straightforward compared to other solutions on the market.

Once I understood how to do it, it was straightforward. You just download EAP, start it up, download Fuse, build an application, and deploy onto it. Those things are quite easy to do, but there were some fundamental knowledge gaps that I had to close, before I could do that. When I first got started using Red Hat Fuse, I hadn't been really deep into the open source Java ecosystem. I was familiar with bits of it, but there were some things it seems they assume you know, things that help you set it up easily. 

It's hard to measure exactly what our deployment time was because we've made a bunch of improvements along the way. But from the time we decided to use it until we got a proof of concept set up—a minimum viable product—was about a month.

It would have been helpful if there were a prerequisite list, along the lines of: in order to use this, you need to know these concepts. Once I got the prerequisites, it took me a month to download it, find some examples, do a little tweaking, build a simple application, put it up, and do a basic test.

The initial setup process is quite straightforward. We are using a standard setup. When it comes to deployment, I just spent four or five years doing the setup, but it can take as much as eight or 10 years.

Initial setup is very straightforward.

The solution is containerized, so deployment is quite easy. Deployment can be fully automated.

It's not difficult to maintain.

The solution is very straightforward and simple to set up. It's not overly complicated or complex. 

I'd rate the overall ease of deployment at a three out of five. We deployed over the course of one year.

For maintenance, we have two or three people that can handle anything related to that. We don't need any more than that. 

The installation and configuration process is simple.

The initial setup was pretty straight forward and there were quite good guides on the internet. The web guides were pretty straight forward. I found it was quite easy to set up and implement.

Red Hat Fuse is very easy to set up.

The installation is okay. Because we have a team who does the OS installation for the client, we don't have much concern. Because it is handled by a separate team I don't have the details with me. We don't have much concern about the installation.

The solution is easy to set up and use if you understand the philosophy behind the framework. Deployment was not a problem because it uses use containers, so I was able to use the source image feature integrated into Openshift. 

As long as you have the source code on GitHub or GitLab or a Git repository it can be deployed in five to seven minutes.

I find the initial setup to be easy. However, some people look for other tools because they don't like the command-line interface. The typical deployment takes about two weeks. This includes getting the machines.

From the point where we have the machines and understand the requirements, it takes no longer than two hours to set up and deploy.