Mule Anypoint Platform Reviews

Mule Anypoint Platform is used for the integration of different services or customer databases with Microsoft solutions.

The most valuable feature of the solution is a huge list of available connectors for a lot of different platforms, which we can use very easily.

It would be better if we had a clearer view of the solution's future releases. Mule Anypoint Platform is migrating to a new JDK, and the old JDK won't be supported within a year. Currently, we do not have a calendar or scheduler about when all the connectors will support the new JDK 17.

I have been using Mule Anypoint Platform for about one year.

Mule Anypoint Platform is a pretty stable solution.

I rate the solution a nine out of ten for stability.

For the moment, smaller clients would consider choosing MuleSoft as their integration platform. As a rule, the Mule Anypoint Platform is more suitable for middle or large clients.

I rate the solution an eight out of ten for scalability.

MuleSoft provides custom support for every client. You can list your account and have open tickets if you have any problems. We have pretty solid technical support from MuleSoft.

Positive

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.

With ready API, the solution can be deployed within a few minutes. If you don't have an API at all, a day will be enough to deploy a very simple but useful API from scratch.

Currently, MuleSoft is moving from the license type to the pay-as-you-go type. The solution's pricing, as per the old approach, is expensive. That is the main reason why we don't have a lot of small-sized customers. With MuleSoft's new approach, we will have new opportunities to integrate small businesses.

The solution's API Designer and API Manager have improved the management of our client's already established APIs. The most valuable features of the solution are Design Center and Runtime Manager. Mule Anypoint Platform provides some basic security approaches, including HTTPS protocol and secure configuration opportunities.

My recommendation to users is to use already described or already propagated best practices that help very much in development. The best advice for developers is to be part of the community. MuleSoft has a great community, including different channels or meetups that could help you a lot in certain cases. When you have some problems, you can address any developers, and they will be ready to talk to you.

Overall, I rate the solution a nine out of ten.

We use Mule Anypoint Platform in our company for API integration, API orchestration, and other related things.

Mule Anypoint Platform's valuable features are its flexibility in terms of deployment and its SaaS capabilities. One of the solution's features is its connectors, which allow for any specific integrations within any other package software. Mule provides a lot of connectors for integration purposes.

I think Mule Anypoint Platform is one of the market leaders, so our customers prefer it, which is why I also use it.

The solution's user interface has shortcomings and can be made much better. Mule Anypoint Platform can be made more user-friendly so that people with lesser technical knowledge can understand the product. Mule Anypoint Platform can get too complex for non-technical people.

I have been working as a system integrator using Mule Anypoint Platform for two to three years.

It is a scalable solution.

My company caters to the needs of medium-sized businesses.

Mule's technical support is good. I rate the technical support between eight and nine out of ten.

Positive

Regarding Mule Anypoint Platform's installation, I can say that since we use the SaaS platform, we didn't face any issues with the installation of SaaS modules.

Mule Anypoint Platform is a SaaS system. The platform is available, so you just configure it and don't need to deploy anything. You just have to configure whether you want high availability, DR, or anything else. Otherwise, there is nothing much to deploy since it all falls on the SaaS capabilities.

We have only three engineers required for the configuration and adaptation of the product.

Price-wise, it is a good product since it is reasonably priced.

The product's maintenance part is easy and requires only one person.

Overall, I rate the solution a ten out of ten.

The solution is a middleware integration tool. It's a deployment part where you deploy your Mule applications and also use Anypoint Studio.

It's like other integration tools like TIBCO. 

Mule Anypoint Platform has a good feature for batch processes where the internal tool handles everything. You don't have to handle it by yourself. If you have a large amount of data that needs to be processed, then batch processing is a very helpful part of Mule.

The product is quick to deploy and pretty straightforward. 

It can scale. 

The pricing is pretty good. 

The stability could be better. That said, they are also getting stabilized as part of increasing the versions and working on that. Previously, Mule version 3 was, of course, very unstable. However, now, version four is pretty stable now.

There have not been very good resources to help us find solutions to issues. 

I've been using the solution for around two or three years.

The stability is getting better and continues to improve, however, previous versions were quite unstable. 

It's a scalable product. If you create an image, a docker image, then you can scale it automatically. There are no issues.

We have onsite people who can help with the technical support. They have access to Mule support. I have sent a couple of queries to them, and they have contacted Mule to resolve any issues. I personally have not contacted Mule support directly.

I'm familiar with TIBCO. TIBCO has a PW container edition, and they're similar. However, PW is using expert language for internal and external transformation. Mule is using the database transformation. That database transformation, it's a totally new language. If you want to use the Mule, then you should have experience in that first.

Mule is a very good competitor of TIBCO, and Salesforce has acquired Mule. So the market has also grown drastically for Mule. 

We may have also moved based on the price, of which Mule's is better.

If they used XPath, XML query language, instead of DataWeave, it would be ideal. That way, our users don't need to worry about knowing a different language.

The initial setup is very simple and straightforward. It's not overly complex or difficult. 

If you're deploying your cloud hub, then it takes time to deploy. That said, if you have that setup on your private crowd, then it takes a couple of seconds or a couple of minutes. It's very fast.

While I'm not sure of the exact cost, it is reasonable, and less than TIBCO.

We are a Mule partner. 

When working with customers, we use both cloud and on-premises deployments. 

I'd recommend Mule to others. It is good in web surveys, REST APIs, and is easy to use. Also, they need to be aware that with Mule, they will have to understand the  DataWeave expression language. If you use DataWeave expression language, then the processing time and performance also increase.

I'd rate the solution eight out of ten. I've used the application heavily and taken projects to production. I know it well. 

We are customers of Mule.

This is a good platform for designing, flowing out APIs, and then doing API-based integrations. It also offers a lot of adapters for commercial products like Salesforce, SAP and the like. It has good monitoring abilities. If you use it for API management, security monitoring and things like that, it works well at the experience API layer.

One of the issues I have is that Jira tries to be more than an API-based integration platform and it encourages writing of Java-based applications underneath the cover, even though it's not meant to be an app service, so it's slow. That's how they try to sell it. The solution has three layers; the experience layer, the process layer and the system layer. The system layer is used to connect the systems; the process layer can be used to create processes like transformations, logic, etc.; and the experience layer is used to interface with whoever's going to consume it. The problem is that the process layer is not efficient. It acts like an interpreter and interpreters are slow, and if you give it some path like converting to a 100 kilobyte file, it takes 15 times more memory than if I just wrote a program 

When you try using it for the processing layer, it doesn't work well. We ended up pulling back to .NET for our own internal microservices that do a lot of processing. We use the .NET microservices as the process layer, because we know it's faster. Then we plug it into Mule to experience the API interface and that's when we need to make a choice, do we put our system APIs right through our microservice, or do we use Mule as a system API layer, but then let it interface with our process API. We just had to make choices.

I've been using this solution for two years. 

The solution has threading, but it has the interpreter feature which I think slows it down.

The technical support is not great and documentation is sparse. You really have to rely on the community, more experienced MuleSoft users, who know the strengths and weaknesses, rather than relying on the company. You can get an architect to assist with implementation.

It's an expensive solution and then you have to try and find a MuleSoft engineer, which is even harder.

The issue seems to be the way they've positioned the product, advocating the experience layer, process layer and system layer through Mule. As it competes with the likes of webMethods, it rates as an eight out of 10. As an end-to-end solution, however, I would rate it a five at best. 

Our company's clients are all from different domains. We use the platform for integration and API management.

I have a background in Java and in the past, there were some issues whenever we had to integrate with the applications. You had to get the business logic and sometimes it took months to integrate the record. With Anypoint Platform, it is very easy to do that. You just need to do a small drag-drop and a small transformation which saves a lot of time.

The most valuable feature is the variety of characters Anypoint Platform has. It is very scalable and customizable.

In terms of improvement, the deployment time could be a little shorter. Other platforms such as Boomi or SnapLogic are much faster to develop. Anypoint Platform has added the option to generate flow online, but it still needs some improvement. It should give better control over account management. Mule Anypoint Platform includes an API Manager and it has a strong ESB. However, the API management capabilities of Apigee offer more advanced and dynamic features for managing APIs. 

Additionally, Mule should work on reducing the complexity of their platform and providing more flexibility for users. Those who are not well-versed in Java will have a hard time with the development of Anypoint Platform. While it offers connectors, the connectors have limitations. It should offer features that can be customized by users, allowing for greater adaptability, and offer customization options within these connectors, to make it easier for users to tailor them to specific needs. Platforms such as Dell Omni and SnapLogic already provide solutions for these problems and allow users to easily plug them in and start working.

I have been using Mule Anypoint Platform for eight years.

I would rate the stability of the platform a seven out of ten. There were situations where specific solutions or connectors were not available, and the support team suggested using workarounds. They advised me to create my own ideas and come up with a solution. This lack of immediate solutions can be a limitation of the platform.

I would rate the scalability of the platform an eight out of ten. There are approximately 300 users of Anypoint Platform at our company and we plan on expanding.

The technical support is good. I would rate it a nine out of ten.

Positive

I have previously used Apache Camel and Dell Boomi but I am also currently using Ab Initio due to client requirements and the need for a faster time-to-market for clients' projects or products. Using a team of ten members, it took around 24 months to complete the migration of approximately 2,000 APIs with Anypoint Platform. Ab Initio only required nine months to accomplish a similar task.

I would give a seven out of ten for the easiness of the initial setup. The deployment takes about two minutes which is acceptable. We handle deployment ourselves. We use tools such as Jenkins or Bamboo and it can be time-consuming since it initially involves scripting.

In terms of pricing, Anypoint Platform is on the expensive side. I would rate the costliness an eight out of ten.

I would definitely recommend Anypoint platform to anyone who is considering using it. Its main flaw is the costliness. Overall, I would rate it an eight out of ten.

The solution is used as a middle environment as we have our own database settings and PostgreSQL database. If an API requires some information then they need to go through Mule Anypoint. We are also trying to implement our own DataGraph. 

In our company, we have some other ETL tools but comparatively, MuleSoft is much more compatible in many other ways for data transformation. MuleSoft can handle a lot of different types of data. So even if something is not available, there are some workarounds, and this is professionally advantageous. 

I have a lot of resources as a developer and I don't want to always ask Mule for help. There are a lot of online resources which can be referred to easily even as a beginner, which is a positive.

Most of the people who work here are long-term employees who are much more versatile in German, than English, and MuleSoft supports the local languages. That was one of the positives and was why Mulesoft was considered beyond its scalability and other functions. Whenever we need some support in our local language, we get it easily. They also have an office in Germany and if a person is unable to contact them by phone, they can go to the office in person.

The initial setup should be made easy and the documentation should have some guidance. 

I have been using Mule Anypoint Platform for two years. 

The solution's stability has increased over time. 

It is a scalable solution. Presently, five to ten people use the solution. 

The technical support team is quick with their responses and are prompt in providing a solution. 

The initial setup is complex as there is no documentation that can guide you. There are professionals to help but they charge a lot.

I would recommend others to use the solution because it is easy to use. If they want to learn, there is a free course available on the website for developers. At the same time, even if you are not able to get some information readily available, there are a lot of other resources that are available online. 

I rate the overall solution an eight out of ten as they are still improving. 

We are using the solution for building business logic. It's like having a particular private cloud service that we can host on our premises, which is less cost-effective than Microsoft Logic Apps. It provides storage and data integration in a very good manner.

The solution's deployment and proxy processes are very good.

Although the solution's proxy design and process are good, it faces connecting issues because it lacks data integration. You have to filter the data before integrating it.

I have been using Mule Anypoint Platform for around one year.

I rate Mule Anypoint Platform a nine out of ten for stability.

We have to reintegrate it and create another structure on the same file instead of modifying the base one. We have to create other versions also. The solution's scalability is questionable compared to Microsoft Logic Apps.

Around 10 to 20 users are using the solution in our organization.

I rate Mule Anypoint Platform a six or seven out of ten for scalability.

The solution's technical support is not so good, but they are trying to provide on-time support. They take around 24 to 48 business hours to provide the solutions.

I rate the solution’s technical support eight and a half out of ten.

Positive

On a scale of one to ten, where one is difficult, and ten is easy, I rate Mule Anypoint Platform ten out of ten for the ease of its initial setup.

The solution's deployment takes around five to seven minutes maximum.

Firstly, we have to understand how we can integrate with the clients provided, then build the proxies of APIs and deploy from Anypoint Studio to CloudHub. A single person was required to deploy the solution.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the solution's pricing as four or five out of ten.

As it is free of cost and we have to take an enterprise license, there is probably no fee.

For the big layer ones, Mule Anypoint Platform will be better than Microsoft Logic Apps or any other integration platform.

Overall, I rate the solution a nine out of ten.

We use the Mule Anypoint Platform for API management and integration.

I am not an end-user of the platform because I'm an architect, and we simply evaluated and deployed it for the business to use. I am not able to provide platform usage analytics.

The ability to define multi-tiered APIs and reuse them is a fantastic platform feature.

Code quality, Code Security, SaaS, and DaaS security, can all be improved.

We recently onboarded and we went live only in the month of February. We are still new to the platform. 

We have been working with the Mule Anypoint Platform for just three months. 

So far it has been good. We are still evolving for broader usage of the platform.

Mule Anypoint Platform is a stable product.

We haven't gotten to that layer yet, but I believe it is scalable, based on the description that we have.

It's a new platform, a new setup in Azure, and I don't believe that we have yet met the scalability criteria. We are still attempting to consume the platform's threshold, which we have acquired.

Mule Anypoint Platform is not being used by a single department. It is being used by the entire organization.

Technical support is both helpful and supportive.

We used DevOps to deploy. We have set up the pipelines on Azure.

I haven't deployed any directly, but deployments can be done within minutes.

It is easy to set up. We have excellent documentation on the deployment and configuration steps.

I am not aware of the cost. It is completely managed by the vendor management team.

They should be knowledgeable about their industry. They should leverage the platform's use cases and try to deploy it only when it is required.

I am a client of this product.

I would rate Mule Anypoint Platform an eight out of ten.