The Anypoint Platform has matured significantly since its inception. It now has API managment, analytics, dashboards, self-discovery, and multiple deployment options.

As the feature set has gone up, so has the price. It's starting to price out small to mid-level customers.

ease of use cloud support Java based re-usability good customer support Scalability

API Manager - Helps in managing the APIs right from applying in-built policies to creating custom policies. Create proxy on top of your applications seamlessly. In-built load balancer as well as customization option. VPC- Able to create a private network of your applications and allows limited access to some of the applications Runtime Manager - Deploy your applications either on-premise or on cloud. You have option to choose your own environment. Anypoint MQ- Enterprise feature messaging system. Anypoint Studio - Eclipse based IDE where you can design the flows, debug, run them, create unit test cases and also use mocking feature. Anypoint Exchange - It helps sharing your API contracts ( WSDLs, RAML ), APIs, etc easier. Anypoint Connectors - Many in built connectors which help connecting to many systems like SAP, Salesforce, Workday, Twitter, AWS, Mainframe, etc. There is a provision to create custom connector too. It is Java based so we can leverage all the reusable libraries Java has to offer.

Pricing is not very good. Need more features in API manager like payload limiting, debugging is weak, etc.

Quick integration of enterprise systems, legacy applications and thick client applications. Easy maintenance of APIs.

Quick development APIs using the API Manager and Anypoint studio, also quick configuration tools are provided by Mulesoft.

API Manager should be able to provide automatic customization of alerts. Undeployment of APIs and Mule ESB services are taking more time in MMC.

1. Mulesoft can be used to provide an integration platform to a large number of systems like Salesforce, ODBC, JDBC, SAP, Mongo DB, etc. 2. A large number of out of box connectors are available in the market place to be used. 3. Ability to write custom connectors to meet the integration needs of the client. 4. Excellent option to develop microservices and real-time integrations

Not as robust in handling large data volumes, Informatica is better in that respect.

We have developed business solutions for a wholesale site to handle orders and trigger mailers.

The best thing I liked about the software is its ease of use with version 3. Able to develop API solutions very quickly with a RAML file and the cloud hub deployments.

Documentation was missing few details for connectors. Also the limitations with community version was challenging to develop solutions which require transformations.

My company uses this platform to maintain some integration services and to publish these to other companies.

It's a fantastic tool to create APIs or microservices really quickly if you have the rest of your services in the cloud. For example, you have the possibility to create some microservices to connect your Salesforce platform with your Office platform or your ERP. It implements a fantastic and simple user interface to help you in the process. His knowledge base and his blog with the examples that you can find in these are really fantastic.

At this time my only cons are to move the MuleSoft on-premises processes to the CloudHub because these requires some adaptations to run in Anypoint Platform.

From the cloud we perform the monitors of our ESB, the integration is of another level thanks to Anypoint Platform.

We are delighted with the use of the integration platform, the connectors are ready to use. The dataweave is excellent with its ESB feature. The watermark concept for great batch processing.

When batch processing is done extensively causes delays, it represents a big problem at the time of integration.

It was an exceptional experience and very easy to use.i love it

It gives perfect monitor tools.It's easy to use

It's difficult to find people who already know the platform.Design center acts weird sometimes.

One single platform to handle apis and integrations

It can be quite expensive initially. RAML and studio have to be learned.

Good

If you want to make your api and the things where api is used this is the best platform

Learning can be bit difficult at the beginning.

Few Advantages that Mule has over other products are :- Mule has a large collection of different connectors to connect and integrate diverse systems. It is said like it can almost connect anything. Mule is very lightweight and easy to use compared to other esb. Since it is mostly Java based, so, it becomes very easy to use and build custom components. Most important is that, Mule is a pure esb, where other products comes with other functionality and platforms and esb is one of the part of the product. (eg WSO2) Mule is graphically based unlike most of other esb, where the flows are mostly configured in XML (Apache Camel or Spring integration) Mule is less expensive compared to most of other products. Even community versions are available, which will not cost you anything. Mule earlier had a problem of its small size of its community. But nowadays, Mule community is expanding like others. Mule, as I mentioned is easy to use. for example, if you want to expose a web service and need to do various transformations with payload, you just need to concentrate on your java implementation classes or you Mule flow. Mule will take care of exposing the service to an endpoint and you don't need to write any code for that. It also has wide range of transformer that will take care of transformation of your payload and also other functionality like orchestration, routing etc and will be easy for you to implement There are more or less other advantages, you can explore more to get it . More or less choosing an esb depends on your requirement and budget.

Data Mapping is the feature i like most in this software, there are many feature which are as follow are the best for my project. Debugging suppor,APIkit RAML Support

RAML Support, we can import RAML files for your APIs that are managed in the Anypoint Platform by the API Manager and keep them in sync with the platform.While working with a RAML file, you can also view an embedded interactive API Console that's automatically built from the resources and methods described in your RAML.Handle complex data mappings and transformations through the Transform Message component, that leverages the powerful DataWeave language. This component allows you to create your transformations both through a simple drag and drop visual interface or by coding in DataWeave to unleash all of the language's potential.

First of all the GUI is Good and easy to use, Mule palette has the connectors needed and if you want more connectors go to exchange and u will good huge number of connectors for each need of the requirement. We stay focus on our main service, while experimenting new services by trying connectors or even develop our own connector. Development is made easy with this drag and drop with very minimal coding based on the requirement.

1. Runtime Manager- Very easy to deploy the build on cloud and manage applications. 2. Exchange - Provides wide range of pre-built connectors, APIs, Examples Etc. Along with these you will also find the links to source codes and documentation in the github. 3. API Manager - Designing REST base APIs made easy using API Manager. You can also publish and test APIs. It offers secure architecture for managing APIs.

Recent Upgrades are not compatible with old components, we have to rebuild the old code to get with the new upgrades. In memory wise it take little bit high RAM usage.

Mule is by far the easiest ESB I have been exposed to. I have reviewed several others and all of them are very code oriented requiring a rather steep learning curve just to deploying your first project. With Mule and the drag-n-drop Anypoint Studio deploying your first project is very simple. Performing transformations also is very simply with the DataWeave component. This component is very flexible. Its use can be as simple as dragging one field from the input to the desired location in the output. Or it can be complex allowing you to develop functions to retrieve other data, manipulate the provided data or create new data. All in all AnyPlatform is a excellent ESB.

Easy to learn Highly flexible Focused on not only improving technology but being a disruptor in the technology field

Is rather expensive Could use better database integration tools The IDE tends to be sluggish

Mule is one of the tool and platform for java people to upgrade into technical skill. It is easy to use and easy to work in any business workflow. This software is a lightweight Java-based enterprise service bus and integration platform that allows developers to connect applications together quickly and easily, enabling them to exchange data. Mule allow user to connect more service in minimum time. We can easy customize any component base on requirement. We can easy used or create SOAP and Rest services. Mule is one platform which support RAML for restful services.

easily develop business flow and reuse with many system. it does not force any design constraints on the architect to deliver any message. its work on highly distributed environment.

created more thread over the application. As per my experience, the performance of the application is not as much good.

I was able to create RESTful services easily/fast-paced. Able to convert existing xml/json formatted data to desired formats quickly without any issues. Fast, proactive, easy interface. But lacks in scalability. Could not implement robust service. Process archestration is difficult when requirement becomes difficult.

Simple, centralized, end to end web platform. Runtime manager, insights, logs, alerts, policies at single place. Only Flow designer is missing. Although it is included in latest version 4.0, should have come before.

Anypoint designer had some issues with IE, Mozilla. Runtime manager hangs. Reporting of flow analytics should be more in depth. API designer doesn't provide all the features of comparitive tools like swagger. Public portal design should have been more options oriented.