Mule ESB is easy to set up, configure, and change the configuration. It only takes a couple of days to make any changes the client asks for. The longest project we had using Mule ESB was one week.

Since most of us are on the cloud, most clients prefer the cloud, where the entire platform as a service is provided. So, the setup process is very smooth, and there's really no setup needed. It's all cloud-based. For local development work, the setup for the IDE is taken care of by the cloud, making everything easy to set up.

The solution is deployed on an on-premises model.

A six to seven-member team, including one or two managers, is required to take care of the technical part of the product.

Mule ESB isn't difficult to set up, but there are specific procedures you need to follow. Prerequisites need to be in place to set up the whole environment. It's straightforward once you set up the platform.

After deployment, it doesn't require much maintenance. Most things can be automated, so you don't need someone to always monitor the solution.  Ultimately, it depends on your use case. 

We had some initial hiccups following deployment, but since then it's been good. We deployed in-house. 

I rate the ease of setup a four to five out of ten. We have to do it properly, especially with the hybrid integration.

The solution's initial setup is easy.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

The installation time depends on the product being deployed and the size of the application. What we are using at the moment would not require installation of more than an hour. We usually would receive a zip file that we would insert into the server, at which point we could start with the deployment. We have a command for the installation of the licenses and even this depends on the type of job involved. That is all. I would put the installation time at no more than 35 to 40 minutes. 

Development is very easy. Initial setup took two days. We needed to open a firewall, download the necessary things, clean the server, file storage, network storage, and we needed to work on the installation of the servers.

For deployment, we had one person for admin and one person for development.

We have a four-person DevOps team that performed the initial setup, so I wasn't involved, but I think the deployment would be smooth and straightforward because it's on the cloud.

It was kind of straightforward. We had to study their legacy systems and then make some kind of mapping between those legacy systems and the RESTful APIs handled by Mule.

For a cloud-based deployment, there is no need for us to manage anything. It is directly deployable. We build and deploy it. That's all. 

For an on-prem deployment, a lot more installation is required, but it is a very easy process.

The setup is straightforward. It was a fast deployment and took one week.

The initial setup was straightforward as we chose to go with the Mule cloud where the infrastructure was taken care of by them. We only needed to ensure connectivity between on-premise databases/systems and Mule cloud.

Because it's their cloud, the setup is much easier. It would be interesting to see what the setup is like for an on-premise or hybrid environment. It might be a completely different setup. It would probably be more complex because you have to go through certain process to ensure the compliance and the security standards of the organization are met, and that the connectivity is established.

Setup was realy straightforward as the product is well documented. Also, we should mention the efforts of a good and reactive community.

The initial setup is pretty easy. We have multiple applications bounded by that domain, for resource sharing, so it was easy.

In the latest implementation, we decided to start small with a very simple project that we had, which was customer integration between our CRM and ERP solutions. We started with a very small API. It was a small integration with only about three APIs, and that was it. We had success with it, and we ran it. 

Mule ESB is one of the best. It is easy to use and setup. You just need to install their Anypoint Studio. It's very safe for all this. It's in a good rank just for the setup.

Mule ESB was very easy to set up. I did three months of testing Mule ESB before I went into production.

The initial setup was straightforward. We haven't faced any issues with implementation. They've recently simplified the processes. I recall, earlier it was not that easy to set up.

Deployment doesn't take too much time. Sometimes it can be done in minutes. It shouldn't take more than an hour.

The setup was complex, as I came from a different background (IBM products). However, it became smoother down the line.

I used some of the notes and YouTube tutorials that explain the setup. They've simplified the process with the latest version which is a good thing. 

The Anypoint platform is based on Eclipse, so anyone who has worked in Java will find it easy.

The installation is straightforward.

The setup is straightforward in terms of deployment and environment setup.
Just download the "mule-esb runtime environment" zip file and unzip under a particular directory. Then a Mule setup is done. To deploy an application, just drop a Mule app into ${MULE_HOME}/apps along with the properties file under class path, then done.

The initial setup was complex.

Deployment took a week. We were waiting for the team to be onsite.

I would say that this initial setup was moderate.

It is complex to set up because any Enterprise grade middleware needs hardening. This is why we need to set up clusters, integrate with source control tools for continuous integration in different environments like DEV, QA, TEST, and also consider firewalls and internet security.

So other than a DEV Server, the setup is not straightforward. It depends on the organization security/development methodologies and policies.

I would rate the solution's setup a six out of ten and took around three to four days to complete. 

To get an initial setup is straightforward.

1. Write a simple HTTP-based listener workflow.
2. Print whatever you send in a context path in a browser.
3. Dump it in a standalone runtime.
4. Start it.

The initial setup is straightforward and only takes a day, but it looks at many data sources, so you have to be specific about what you need. 

The initial setup was pretty straightforward with few easy steps.

The initial setup is complex because of the Maven part.

The initial setup wasn't that complex, we did it ourselves.

The setup was pretty straightforward.

The initial/basic setup for the development and production environments was fairly easy and straightforward. For complex requirements, you may need some assistance from the experts.

I think the initial setup was straightforward.

The initial setup was straightforward.

The initial setup is very simple. The installation probably takes four hours, on average.

The installation and setup had been completed before I joined the company.

The setup is done with a simple deployable .zip file. It is very simple to set up and run.