Opiniones de Anypoint Platform

Lo que mas me ha gustado del software es que el desarrollo de aplicaciones en esta plataforma no nos ha resultado muy complicado de utilizar. Hemos utilizado JAVA y ORACLE como motor de base de datos para el desarrollo de nuestra aplicacion y asi de una manera rapida y sencilla, hemos podido crear una pequeña aplicacion.

Su curva de aprendizaje puede ser un poco lenta si no has trabajado con ECLIPSE, y la atencion al cliente puede ser mejorable.

Ha logrado satisfacer mis necesidades internas y la de mis clientes

Al día de hoy no existe detalle que impida el seguir utilizando este softaware

Me resulto interesante probar esta herramienta para diseñar , implementar automatizar, redes de aplicaciones

Si no tienes ciertos conocimientos de APIs te puede resultar dificil iniciarte en ella.

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.

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

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.

I love that its a part of salesforce's Integration Cloud which every top company is using right now. This benefit alone is an easy sell because it allows connected customer experiences across all channels
-easily unlock data from legacy systems
-very innovative company with more to come

With anything as you are deep in the development you might run into some bugs but there is enough information out there to deliver for your customers

There are many things to like about Anypoint Platform. Few of them I would like to highlight:
1. Integration Platform: Anypoint Platform is a hybrid integration platform provided by MuleSoft which is used to build application network very easily, structurally and smartly with proper documentation.
2. API-Led Connectivity: Anypoint Platform implements API-Led Connectivity approach to make application network Reusable, Loosely Coupled and more Govern.
3. Layered Architecture: Anypoint Platform follows Layered architecture style in the integration based project in which for each external system we create an API on top of it to expose their data. This API is called as System API and this API is not used normally by any user directly.
Then if required, to merge the two or more than two external system together, we again need to create an API on top of them to expose their data together. This API is called as Process API which is more process-oriented. And then finally we come up with Experienced API on top of Process API to expose process-oriented data so that the end user could get the data from different external systems. So you can see how Anypoint Platform smartly uses Layered architecture style to build out network applications eaisly.
4. CloudHub: This is perhaps the most relevant benefits of Anypoint Platform according to me. Anypoint Platform provides various ways to deploy your integration applications and APIs both on Cloud computing environment and on premises

- 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

I feel Anypoint is a smart tool. Like in other integration tools we need to specify each and every thing manually where as in this based on the location we are placing a palette, it automatically pick up the behavior and do basic thing itself.
Dataweave is a powerful functionality we have in Anypoint studio, which is again very smart palette.
Above all, availability of multiple connectors.

Setting up the project in local that too in new system is very difficult and time consuming. It takes too much time for updating dependencies, mostly maven.

Mulesoft provides the very good different connectors to connect just to give by certain params,
also transform message is powerful feature of Mulesoft which can transform any data format to any.

Some times not able to Debug the flow even after creating the fresh instance of Anypoint Studio,
also there is no hint or predefined Oatuh url each time need to go for particular connector documentation