MuleSoft Anypoint Platform Reviews

Primarily, we use Mule Anypoint Platform for orchestration and workflows.  We also use it when more than two applications have to talk to each other or real-time transactions are required. Another use case is for a triggering mechanism that also requires data transformations.

We like it because of its ease of usability. It is a very user-friendly and developer-friendly tool. The maintenance cost is low, and the overall required team size is also optimized.

The compatibility with vendors can be improved. Microsoft Azure heavily uses single software.

Compatibility with other services or cloud providers like AWS or GCP is not very well defined. This is an area they need to be a little more cautious about.

Nowadays, everyone is talking about Generative AI, how intelligence can be brought into different systems that are ready. If we talk about Mule Anypoint Platform, the system and data are there, but the integration layers are not very advanced. They should bring in Generative AI and other AI platforms because even it will need a lot of self-building intelligence and decision-making.

They have good competition from cloud providers nowadays. There is a lot of scope and innovation competing in that area. 

I have been using it for three years now.

Mule Anypoint Platform is quite stable. It is used across many large organizations, and we have not seen many issues with it. I would rate the stability eight out of ten.

I would rate the scalability an eight out of ten. Mule Anypoint Platform has great capability around different products, including products within the platform. It is a very decentralized kind of solution that can be scaled to very high levels.

We do connect with support from time to time if there are issues. The technical support is good. They do reply on time and take responsibility.

The initial setup is simple enough. 

The product is very expensive. I would rate the pricing six out of ten.

Mule Anypoint Platform can be considered the leader in the market. After being bought over by Salesforce, it now has some added advantages. For any large or mid-level company that is going for multiple applications like SaaS-based applications, ServiceNow and Salesforce, the Mule Anypoint Platform is very useful. Small-scale companies choose other open-source and cloud-native solutions which are much cheaper in cost. 

There are other leaders like Dell Boomi and open-source Kafka, but the best part about MuleSoft is the foundation architecture they use which is highly scalable and reliable. The compatibility for the Mule Anypoint Platform is greater than other competitors. I would rate the product seven out of ten. 

We have a strong presence in various use cases, with the primary focus being on digital integration and API monetization. Our main objective is to help our customers maximize the value of their APIs and generate revenue from them.

We have adopted an API-led digital transformation approach which has already started delivering value for our clients.

The community manager is the standout feature of the Mule Anypoint Platform, as it provides a platform to showcase your API to external parties. It is exceptionally user-friendly and enables external parties to easily utilize and consume the APIs.

In order to set up a storefront, we currently rely on a third-party solution. It would greatly enhance our operations if this feature was integrated into their existing solution.

Some of the functionalities are hosted in the cloud, which occasionally poses challenges when integrating with on-premises applications. Improving this aspect could be beneficial for a smoother and more seamless experience.

I have been using the Mule Anypoint Platform for approximately one year.

The stability of the Mule Anypoint Platform is excellent.

I rate the stability of the Mule Anypoint Platform a ten out of ten.

The solution is scalable. One of our large companies that use the solution has not had any problems.

We have between 20 and 30 engineers, developers, and architects using the solution.

I rate the scalability of the Mule Anypoint Platform a ten out of ten.

The support from the vendor is great.

I rate the support of the Mule Anypoint Platform a ten out of ten.

Positive

I have previously used IBM. 

The system we have is straightforward yet highly integrated. It is a single platform, unlike IBM, where they had multiple platforms and systems to deliver similar value. This complexity made the IBM system challenging to navigate as their technical resources had to learn various platforms, including integration and API gateway, which had different formats. Consolidating these platforms into one unified system would simplify management and reduce complexity.

Setting up the Anypoint platform is a very easy process especially when supported by the Catalyst Launch services from MuleSoft.

The pricing of our solution is highly competitive. While it may not be categorized as exceptionally low, it is certainly more affordable compared to IBM.

I rate the price of the Mule Anypoint Platform a seven out of ten.

We come from IBM Integration Bus background and the decision to adopt Mule was easy after a few engagements with the MuleSoft team.

The initial setup of the Mule Anypoint Platform is simple. My team was trained in only a few weeks. The process of deployment took a couple of hours.

My advice to others is for them to use the catalyst service. They help you get started and gradually let you be on your own.

Mule Anypoint Platform is also highly convenient since my team was able to quickly set up the new team for the initial implementation. Within a few weeks, they began developing independently, gradually reducing the need for external support and focusing on efficiently running the system with internal resources.

I rate the initial setup of the Mule Anypoint Platform 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 are an integrator for Anypoint MQ, based on Mule 4.3, with several active customers. The solution is typically delivered by cloud and there are differing kinds of use cases that we see.

If there is an event-driven architecture in place, then we will use Anypoint MQ to connect the different APIs together (such as the Experience APIs, Process API, and the System API) so as to enable a seamless process while minimizing data loss. That's the main use case seen in our work.

It's easy to use and comes as a bundle package with the Anypoint Platform, removing the need for any complex setup.

Anypoint MQ's capabilities are mainly used for messaging purposes, but it doesn't have typical use cases that extend as far as other Message Queue software.

For one, it would be helpful, from an additional features perspective, to see that it can handle large files of any type, whether image files, video files, etc. And if they would include an SFTP solution such as is available in AWS or Azure, this would be an added advantage for our clients.

Stability-wise, it's okay.

With regard to scalability, there can definitely be improvement. To make it more scalable, there needs to be a change in the upper limit of file sizes for messaging purposes. Currently, it can only handle messages up to 10 MB in size. If that could be addressed, I believe it would help those customers who have to handle large files.

From a technical support perspective, we mainly deal with product-related issues. We used to go back to MuleSoft and ask for support, and they provided if the customer had bought that particular piece of support. We needed to raise a ticket first, and based on that, they provided us the solutions.

But for any technical solutions needed, we would provide them, so we would only get support from the MuleSoft product team. In our company, it's our job as an integrator to provide the support.

It's easy to install, since it comes as a bundle package with the Anypoint Platform.

It is a good product, but for the reasons previously mentioned, there are a lot of opportunities to improve this particular piece of software.

I would rate Anypoint MQ a seven 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. 

I use the solution for NetSuite and Salesforce integrations. 

The tool's visual features are attractive. 

Mule Anypoint Platform is complex for beginners. Users without programming skills will find it complex. It should also improve its pricing. 

I have been using the product for half a year. 

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

I am the single user of the product in my company. I rate its scalability a ten out of ten. 

I haven't contacted the technical support team. 

The product doesn't require the installation of agents. 

Mule Anypoint Platform is affordable. 

You would need programming skills to use the product. I rate it a nine out of ten. 

I think the solution is used to build APIs

The transforming message is an area in the solution that needs to be improved. There is not much information on the internet, and since MuleSoft is new, there is nothing to research or find in Stack Overflow.

They are probably trying to test two layers at once. I don't know how that would be possible. I've been trying to work between something another company left recently. So while testing it, it's been hard because there are a lot of layers, and some of them are not okay. If I could test two locally, that would be great.

I have been using it for a couple of months. So, it has only been two or three months.

It is a stable product.

Previously, we used Cisco in our company.

The initial setup was simple.

I would recommend others to use it because it's very easy to start. Overall, I rate it an eight and a half to nine out of ten.