We didn't have too much time to implement this product. We had a very short runway so we needed the expertise of a third-party contractor to get it implemented. We hired Spico Consulting, and their experts had experience in Red Hat Fuse. There was one consultant in particular who had done work in this space.

They stepped in and helped us build the framework, and the framework helped us to get things working much faster. We only had six months for the framework, then the next year and a half was needed to implement, integrate, and migrate to the new solution.

You can follow any of the API or SOA architecture. In our case, we use API-led connectivity, which is proposed by MuleSoft and Red Hat Fuse mimics that API-led approach. So, you can decouple your services and make an application for the same thing, e.g., we are taking the MuleSoft-proposed model and implementing it on Red Hat Fuse. It is easy.

Once we release the incident setup, deploying the current version will take three to four days, including the verification.

We did a generic deployment for Red Hat Fuse in-house. We didn't use a third party for deployment, but I'm not sure if we'll need to work with one if we have to deploy the solution in a microservice architecture with one service per container, or how we'll go about doing it. That is something that we never figured out, but now that there's a requirement for deploying Red Hat Fuse in a microservice architecture which is something that we have not seen so far, we have to decide on how we'll go about it.

We've had an implementation partner on the Red hat side as there is a bit of a learning curve and we're still trying to work things out. 

The deployment depends on what you are installing and configuring. But typically, it can be done in a matter of hours. For end-to-end things like Kafka, it depends on how you install it because it requires a specific kind of storage. It's not difficult to install Kafka, but you need to prepare the storage beforehand.

If you don't need very high performance, you can do it in less than one hour. But if you want to have highly performant storage, it takes more time to prepare the storage.

In our project, I deployed the solution. However, maintenance depends on what you install and configure. If you have any issues, it's possible to involve some maintenance. If there are changes in your application or business model, you may need to adjust some parameters, like Kafka topics, for example. In general, the only maintenance I do is to update to a new version.

Maintenance is very application specific and how you evaluate them in terms of settings.

Deployment of Red Hat Fuse takes three days to set everything up from scratch.

We did engage a Red Hat partner a little bit, Section6, to refine the design by designing some of the finer parts of it.

Our experience with Section6 was mostly good. Some of them were ex-Red Hat employees. They were professional. They knew what they were talking about, although there were varying levels of experience within their team. Some of them were really great and some of them were not as great. But overall, the experience was good.

We have a reseller consultant who can assist with the initial setup.

We have a mixed team. We have look external help for the developing and supporting tasks.

We only need one person to do the deployment who is from the DB team, so they know about the database and the server. 1% can handle the whole thing.

I did the implementation myself.

Our in-house team is responsible for deployment and maintenance.