MuleSoft Anypoint Platform Reviews

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.

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. 

The tool's use cases are mainly for enterprise-level integrations that require transformations and major publish-subscribe scenarios in which data needs to be published to multiple systems in different formats.

I rate the solution's ease of learning a nine out of ten. It has good documentation and self-learning videos. It promotes usability and provides an end-to-end integration solution with the Salesforce ecosystem

The tool helps with order management and automates the enterprise's orchestration, invoice creation, product maintenance, and product life cycle. The API manager feature helps us configure, secure, and call APIs. 

The tool requires programming language. 

I rate Mule Anypoint Platform's stability as nine out of ten.

I rate Mule Anypoint Platform's scalability as nine out of ten. 

The solution's deployment is 10-20 percent longer.

We have a team to deploy the tool. 

The tool's pricing is cheaper than other RPAs' since it is execution-based. Other RPAs charge based on subscriptions.

I rate the overall solution 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.

We use the infrastructure of the Mule Anypoint Platform to host our application and services on Amazon. We are end-users and I'm a technical delivery manager.

The most valuable feature of this solution is the ease of developing APIs. It's very, very easy and very fast. Anypoint offers good performance and security. 

The pricing should be improved, it's an expensive product. 

I've been using this solution for six years. 

The solution is stable. 

The scalability is good but again, you need to be aware that if you want to scale up your APIs, it requires spending more. 

We're not so happy with the technical support, it could definitely be improved. 

Generally, deployment of one API wouldn't take more than 10-15 minutes. We use CICD DevOps for our deployment strategy and it's carried out in-house. We use this product continuously and extensively.

It's important to be aware of the cost implications of using this solution. Unless you know the extent to which you are going to use MuleSoft, you'll begin with a handful of APIs that need to be developed and then you'll start implementing more and more until you realize it's become quite expensive. 

I rate this solution eight out of 10. 

We use the solution for migration and integration.

There are issues with dead-letter queues.

I have been using Anypoint MQ for one year.

The product is stable so far.

The customer service is not good enough in Hong Kong.

We chose Anypoint MQ because it is a top-rated product in the market.

For the basic setup, we use some local message queues and integrate them with the message queue. It took one year to complete the setup.

We used another tool because it was complicated, and we had to hire a third party to build the architecture. The setup is quite complicated.

Anypoint MQ has stability issues. I have experienced data loss and inconsistent behaviour. The data isn't always pushed to the SQL database. When I put a message in the SQL queue, the data should be static, but it's not. Additionally, clicking a message in Anypoint MQ can sometimes trigger database loss. This instability becomes particularly noticeable when starting or restarting the server.

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