Avis clients sur Anypoint Platform

The ability to load and install for free with some support. The advanced integration and API approach for combining services and other products makes the product extremely useful and quick to test and implement without any financial commitment.

LIke any other free open-software package, when it works, it's fantastic. When it doesn't, or when you are trying to do something that doesn't seem like a common usage, it can seem like you're on your own. It can take a while, solutions can be found, but it can take some time.

Easy to connect to various external systems such as database, File Systems etc.. We can use existing connectors to connect to various external systems instead of writing the code. Amount of time take to develop a application is relevantly less.

Support from the mule soft is not sufficient so far. we need to raise a case if we face a issue and average respond time from mulesoft folks is not fast as would expect. we have faced this problem couple of times in my office.

Provides a mock service automatically

Many bugs in the editor - showing errors where there are none, showing errors on the wrong lines.
Versioning done wrong - no way to keep API definitions in a proper SCM like Git
Sharing not enabled properly in our organisation - not sure why but was told it was due to a "limitation"
I wasted 2 full days doing training that was dull, slow, factually incorrect and we had to help the trainer spot his own mistakes

The ESB is the centerpiece of our learning ecosystem. While not having a front end interface and requiring programming (API work), it's been a tremendous efficiency tool for us. If only we used it better!

It's pretty pricey and the service around it is also costly as that is the main upcharge for businesses who don't have a lot of programmers, etc.

Raml design, exchange to publish the specs, runtime manager to manage deployed API

Design center acts weired sometimes, ask to use newer verify of raml while we self are are editing the the newer version

the possibility to use/search and use connector implements by other

it is quite expensive, for small company is not the right tools

One platform that does it all. What more can you wish for!

There aren't any, I mean it's a little pricey, but totally worth it.

n number of possibility in integration space considering its direct competitors.
Design Center is a mater stroke for creating API specification & API Manager(act as Gateway) which competitors doesn't have.
Graphical flow design which is easy to build and debug.

I don't see any because Mule fulfills much need integration needs

The user interface is very friendly, very complete this integration tool with all the options for setting up the raml, creation, exhibition  and configuration of the API in addition to the part of statistics analysis incredibly useful for making business decisions.

Not all options are intuitive and it is a little uncomfortable to expose the API on the one hand and configure it on the other, it would be better if everything were available in a single section.

If you don’t have an engineering team, this is the way to go on doing ETL. It’s a little bit of the learning curve in the beginning but I think it’s worthwhile.

It’s so expensive but I guess you’re paying for the ease of use from the product.

Best for both ESB and API management
Ease of development with drag and drop approach. Development time will be reduced
Has plenty of inbuilt connectors for cloud and on-premise systems and we can develop our own connector
Supports 4 scripting languages Groovy,Ruby,Java,Python.
Easily integrates with java in various ways
Dataweave support for transformation
Easy designing of API with RAML and Swagger
Supporting of API gateway,policies, SLA tiers
Easy deployment seup in coud and on-premise

When some error occurs while developing, logging is not clear for them.Logging needs to be improved
Unable to debug Dataweave script
Lack of lookup tables support in current Dataweave. Has good support with DataMapper
Need to be improved features in API management
Documentation is good but can be improved
Faced some issues with API kit router while handling with large data.
Synchronising the data from on-premise systems to cloud systems and vice-versa

- Intuitive user interface. It's extremely easy to locate API information and consume analytic information.
- Easy to do create new APIs via RAML.
- Fast and easy deployments and updates.
- Wide range of connectors.

- Customer support can be a bit slow and hard to reach.
- Developer Portals for APIs do not allow for much customization.
- If you manage a lot of APIs, it is hard to keep track and administer APIs since tables do not let you sort using API request date and other variables.

Light-weight.
Scaling down - quick point-to-point integrations.
To the Cloud - CloudHub.

Circular reference is wrongly interpreted during deployment, even though it will not result in loop.

Error-handle processing, deep code programming (directly on the XML), Python, Java and other code separated into the transformations, complete IU for developing, connection with versioning solutions

Prcesses monitoring, task schedule

Drag and drop feature makes it very easy to build flows. very short learning curve for anyone with java background. Open source technology makes it easier to customize something which is not provided out of the box.

Adding additional cloud connectors, which are not shipped with along with it are very difficult to install. The documentation provided for any of the component and or connector is not updated.

- Starts up quick.
- Vm queue
- Eclipse based IDE
- Easily extendable
- Simplest SDK every seen
- Ability to use Hybrid environment

- Minor data mapping change required a development cycle.
- Log cluttering
- To many release, and non backward compatible changes

easy to use ,easily i can deploy my application ,can check logs ,easily can change the worker size as per application requirement , good customer support for any issue

logs are rolled off after some limit ,observed worker crashed issue many times with many of my applications

A lot of out-of-the-box content

Support is not that great.

Paradigm shift. API led connectivity vs. monolithic solution. Network of APIs is the way to go, and with right design approach you can have APIs which you never have to change.

documentation some time is harder to find, compare to MicroSoft technologies where there are tons of examples and sample code, it is sometime hard to get your specific question answered.

1. Application Program Interface concept.
2. Playing as very good role in Integration platform compare to other Integration tools like TIBCO ,Web methods and Oracle Fusion ... etc

1. customer support
2. product patch versions
3. Need to introduce some of connectors or adapters for establishing connection between mule to destination applications or systems like SAP......etc

Ease of development, deployment and monitoring of integration applications.
API security.
Abundant Connectors.

Anypoint Platform cloudhub UI needs drastic improvement.Anypoint MQ can not be open in IE browser.Pls make it compatiable with IE browser also.
Cloudhub logs need to enhance with some new functionalities like archieving.

Any point studio is awesome with a lot of components. It also has a lot of out of the box connectors.

RAML editor can be plugged in Anypoint Studio as currently developing RAML is challenging and using online or trial version of the other softwares

Easy way to create API. Easy way to do any bulk data operation. Easily we can connect with any thing

heavy software takes too much cpu so our system should have good configuration otherwise it would be very hard to use it.

new technology within one IDE.Its most effective, most competitive, we can learn a lot of thing if we have intention to learn.

lot of things we need to learn to become a expert, proper time, and dedication is required for this technology.

The drag and drop feature, of course, datasense, data mapping for transformations. Does the heavy work of connecting to different services, allowing programmer to focus on programming things only.

Sometimes clicking on message processors don't open properties tab, you need to click on some other and then click back on the processor you want to, it happens especially with transform message.
Sometimes the changes are not reflected when deploying, so you have to delete .mule folder from workspace and launch again.