Mule Anypoint Platform Reviews

We are a solution provider and we have been working with a couple of people that use this platform It is used for API integrations. It helps to integrate systems together, working towards modernizing your IT, and putting systems into the cloud.

Mule works very well with Salesforce and CRMs.

Better documentation, in particular with respect to the initial setup, would be helpful.

I have been using the Mule Anypoint Platform for more than a year.

This is absolutely a stable product. It is going to stay for a long time.

Mule is very scalable, and it is one of the prime reasons we use it. It makes for better integration when you are scaling up.

We have been getting good support from the team at MuleSoft.

The installation requires some expertise and your resources need to be certified. It is not a typical solution, so you need to have some knowledge.  

We are a consulting group and deploy and maintain this solution for our clients.

There are several of us and the company founder and CEO is a techie, so this is his line of business.

The license fees are a little bit expensive but you get a lot out of it. Mule is not the cheapest integration platform out there, but it deserves the price we are paying.

I would rate this solution an eight out of ten.

The solution's market place for different kinds of integration platforms is the most valuable feature.

Technical support needs to be improved, especially when you need help with more technical aspects of the solution.

The solution is stable. We haven't had any serious technical problems.

The solution is scalable.

We didn't previously use a different solution.

The initial setup was straightforward. The deployment didn't take long; maybe a few days. You only need a small team of three to five people for deployment and maintenance.

We had consultants assist us with the implementation.

We have seen a return on investment, but I cannot speak to the details.

There are no other fees beyond the standard licensing costs.

We did evaluate other options. The community around Mule and the platform were big selling points for us. There's a lot of great technical articles that help. We also had several other similar cases, which were already running on Mule. 

We use the public cloud deployment model. We used to use the on-premises model, but we moved over to the cloud.

I would advise others considering using the solution to do some kind of small project to start. Then, when you scale to a more production-like architecture, that's when you need the support and help. If you don't have it there in-house, you need to find that support. All of those tricky details which you maybe didn't do in that first phase, you need to do, and proper support will help. Make sure you have it.

I would rate the solution eight out of ten. I'd rate it higher, but we got into some technical setups where we needed more expertise. We had to wait for that expertise. We got it, finally, through consultants, but we expected to get it more from the company. All they could do for us was point us in the direction of where we could get help.

We primarily use the solution for the interconnection of applications in our microservices architecture.

We are very satisfied with the DevOps support.

Technically speaking, the solution is quite good overall.

The initial setup isn't too difficult.

The stability of the solution is good.

We've found the scalability to be good.

Technical support is great.

The solution is very expensive. They need to work on the pricing.

Technical information is not always easy to find. They should work to make it more accessible. 

I've been using the solution for one and a half years at this point. It hasn't been that long.

The solution has proven to be quite stable so far. there are no bugs or glitches that I have experienced and the solution does not crash or freeze. It's reliable. 

The solution is scalable. If a company needs to expand, it can do so with ease.

Typically, this solution works best with larger organizations.

We've found the technical support to be very good. They are helpful and responsive. We've been satisfied in general.

Before this product, we used webMethods. We switch solutions due to a customer requirement. 

The solution has an average amount of complexity. It's largely straightforward. A company shouldn't have too much trouble with the implementation process.

The pricing is pretty high.

I'd rate the solution at an eight out of ten. We've mostly been very happy with the product's capabilities so far.

Our primary use case for this solution is for our supply chain network and integrations. I'm an integration architect and we are users of Mule Anypoint. 

The API management portion of the solution is great and the most valuable for us. 

With regard to the integrations, I'd like to see something similar to the features you find in Dell Boomi related to the intelligent management data and intelligent mappings. Those would be helpful improvements that would help developers. For beginner users with little technical knowledge, some low code would help. 

The solution is Java oriented but doesn't require Java knowledge which is good. But when you are debugging something or when you have other issues, it's important to know a little bit about that. I'd like to see some simplification. Anything that can be automated in the Data V area would also be helpful. 

I've been using this solution for three years. 

The stability is good although we sometimes face issues with debugging and Java errors that we get in the Mule runtime. Batch components and debugging require Java knowledge. I know that the interfaces you find on some other products are more stable than this and our issues come from the Java troubleshooting and monitoring. 

The scalability of this product is good. We have a team of 15 developers who use it. I'm an API architect and work more with DevOps but the solution is also used by others such as platform architects. We work at analyzing our requirements and then assist our team and developers. It's the development team that maintains the solution. We're looking to expand our use of this solution. 

We haven't had any issues with technical support, they're quite good. 

We had some issues with the initial setup. It's a balancing act and it requires some basic technical knowledge. It took some time to debug. We initially carried out a manual deployment and then used the Azure DevOps tools to do the automation. We used Ansible for the deployment. 

I would rate this solution an eight out of 10. 

It is very easy to use for building connectors. It comes with a lot of connectors. For example, it has different adapters for NetSuite, which are very easy to use. It also has Salesforce connectors. 

The object store feature is also really easy to use. Mule Anypoint Platform is also good in terms of performance and how it is managed behind the scenes.

It has different types of subscriptions. For platinum or lower subscriptions, there are not too many things that can be done. We don't see many features. They should release a basic version that has logging and monitoring features. These features should come with Mule Anypoint Platform for free instead of making customers pay separately for these features.

Its dashboard can be improved to have a lot of charts so that it is easy to visualize information. The utilization part can be improved. The dashboard is good currently, but it can be better. Other solutions like Elastic have a good dashboard, and they allow you to administer the product from the UI. Currently, for RTF, there is a different dashboard or utility. It would be good to include the same utility in the cloud solution.

It would be good if there is a centralized repository that includes the links to the information about various troubleshooting issues. The documentation is there currently, and it is good, but the troubleshooting information is too scattered. We have to go to different links to find troubleshooting information. This kind of centralized repository would be helpful for new customers who are implementing this solution. It will be helpful to see different kinds of issues that can occur.

I have been using this solution for six months. We are using the latest version.

It is pretty stable. We don't have any issues with its performance.

It is easy to scale.

I didn't contact them. My current role does not allow me to directly contact technical support.

It is pretty easy. If it is an on-premises deployment, then you need to set up a few things. If it is a cloud deployment, there is nothing to set up. The RTF deployment is quite complex, and it has some prerequisites. 

We work on all three models, that is, cloud, on-premises, and RTF. Nowadays, people are going for cloud solutions. The cloud model is good if you do not have any compliance issues for storing customer information on the cloud. However, if you have compliance issues, you can go for on-premises deployment. There is also RTF deployment, which is a new and very stable option. People who have used the RTF option found it to be very good.

I would recommend this solution. I would rate Mule Anypoint Platform a nine out of ten.

We provide the solution for the clients. 

It's mainly used for hybrid integration solutions. Cloud to cloud and cloud to on-premises scenarios.

I have found several things most valuable, including its very quick implementation, that you can use a lot of out of the box templates, and lastly that it is a very mature product, especially in hybrid integration. It's easy to use.

Overall, I think they're keeping pace with the changes that are happening. I don't have any complaints about anything. They could just improve implementing the integration.

I would also like to see some kind of monetization of A-P-S. That's important.

I have been using Mule Anypoint Platform for three years.

It is a stable product.

In terms of scalability, it is easy to scale and expand. It has the capability to scale in regards to run time, as well.

The clients that we're working with are mostly medium to large and use it on a daily basis.

In terms of initial setup, if it is cloud based, it is very simple. If it is on-premise it is complex.

An on-premise setup requires special skills and you need a lot of professional services.

I would advise anyone interested that you need to make sure you're using the right patents. I think that's important.

On a scale of one to ten, I would rate Mule Anypoint Platform an eight.

I worked for a MuleSoft partner for four years before going independent mid 2017.

MuleSoft offers with the Anypoint Platform a unified platform for API management and an integration Platform as a Service (iPaaS) as well as an on-premise Enterprise Service Bus pattern.

The iPaaS and API management are offered on CloudHub, MuleSoft's SaaS offering, and is located on Amazon Web Services. API management and the iPaaS run-time can also be deployed on-premise or in a private cloud. The run-time manager, Anypoint Runtime Manager (ARM), for monitoring and alerting on the run-time is located by default on CloudHub (AWS).

The API management capabilities are very mature and allow an organization to re-use microservices. It enables efficient self-service for connecting (external) API consumers through Anypoint Exchange. The API Manager includes out-of-the-box policies that can be used for rate limiting, throttling, and security.

The platform support High Availability, High Reliability and High Performance if the required patterns and network topology are followed.

The platform offers over 200 standard connectors for applications and technology, such as HTTP(s), databases, SOAP, XML, and REST, as well as premium connectors for SAP, HL7, EDI, etc.

Integrations are configured visually by dragging and dropping them on a canvas, but they do sometimes require some coding by Java, .NET or Groovy.

The API management, iPaaS and on-premise ESB run-times are based on the same source code and allow an smooth in-time move to iPaaS, if desired, with minimal changes to the existing configuration and code.

The recent Q3 2017 'Crowd' release of the platform included the flow designer, a browser based visual zero-code IDE for citizen integrators, and additional functionality for API management.

MuleSoft's release calendar is rather conventional with two major, two minor releases and hotfixes in between. The competition sometimes offer more rapid release cycles and provides improved and new functionality with a faster time-to-market.

None.

None. The minimal subscription offered is already highly scalable, and one can always upgrade to more processors, if required.

Good, but a bit formal with following process and policies, but that can be the case with technical support anywhere.

Point-to-point connections. An iPaaS and/or API management offers more advantages, such as shorter time-to-market, less staff required for development and maintenance, less incidents on support, etc.

MuleSoft has a pure and dedicated vertical focus on product development for integration with their API management and iPaaS offerings, which can be consider as a plus.

Very quick and easy. An environment (development, test, UAT and production) can be set up in a couple of hours on an on-premise infrastructure or private Infrastructure as a Service compute cloud.

I worked at a MuleSoft implementation partner in the past that did full implementations and support as well as enabling a customer in-house IT team on the platform.

As far as my experience goes, the vendor team is also strong.

The ROI is very good with this integration platform as is the case with similar iPaaS and API management offerings in the market.

The TCO of an application landscape is heavily reduced by phasing out possible existing middleware, custom point-to-point integration, underlying infrastructure, and reducing technical debt.

Vendor lock-in of existing IT suppliers with possible (legacy) applications and heavy customization can easily be reduced by following the proper implementation approach and by this decoupling Line of Business applications in a landscape. "Legacy modernization" is another use case, that can be realized with the platform.

The API-led approach of MuleSoft offers a very cost-efficient model and re-use for implementation and support of microservices, APIs and (generic) services when followed correctly, and is fully supported and enabled by the web engagement tools of the platform (Anypoint Exchange, Anypoint Portals, and Anypoint Design Center). The approach results in a decrease of maintenance costs and time for internal IT departments and external IT vendors and frees up time in an organization for innovation.

Licensing can be complex as is the case with most iPaaS/cloud offerings.

I would advise on making an overview of the type of connections needed, technology, and applications used and to match this to the licensing model and take the time for the explanation on the licensing model. What is the minimal licensing model, which parts are mandatory, when can you scale up or down, etc. One needs a full picture to understand it.

MuleSoft is also known for Mule ESB, their initial Open Source offering, and this one is still available. It should not, however, be considered for enterprise class use cases as it does not include the required out-of-the-box connectors and requires heavy coding in Java. The Anypoint Runtime Manager is also part of the Enterprise Licenses and no management console is thus available for Open Source making it a black box on production as is the case with custom point-to-point middleware.

BizTalk, Talend, and WSO2.

Using Mule ESB, we have solved all of the client’s integration needs. Because it was developed based on the Java Spring framework, it can easily be understood by folks with a Java background.

As I have used more ESB features, I have grown to love this more than an API gateway. Developing and exposing your API using Mule ESB is also quite interesting and easy to use.

Some improvements are required in the batch component in case of errors in the batch steps and when processing a large volume of data.

There was an issue in the previous version, 3.6. They have improved and it has been stable since version 3.7.

The initial setup was not complex for folks with a Java background. It can be bit complex for people who only have tools experience.

It is a very good ESB tool for integration. It is easy to learn and their documentation is very well organized.