Opiniones de Anypoint Platform

Nuestra experiencia general con Anypoint platform ha sido muy satisfactoria, nos recomendaron este software para desarrollar una pequeña aplicacion que necesitabamos en nuestra empresa, y con ella lo hemos conseguido de una manera rapida y sencilla. Como ya estabamos acostumbrados a trabajar con Java no nos ha sido muy complicado utilizar este software, ademas el poder utilizar la base de datos de Oracle, que para nosotros es una de las mas potentes, nos ha facilitado el trabajo.

Ha sido muy gratificante a nivel de usuariosy clientes

This was the reason we could do what we did with real AI, machine learning, and hyper connected api's.

API management

I have been using it for 1.7years it works efficiently and is easy to use and has lots of features to explore

Very good. Computer programming fundamental are no needed to start working in Mule. It is a graphical flow designer and rest is UI based.

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.

While the Anypoint Platform is a newcomer to API management tools, it still manages to be feature rich and offers a great deal of resources for both API development and deployment needs. As an ESB, it offers a plethora of connectors for making our various enteprise systems work with each other while exerting minimal effort to do so. The interface is extremely user friendly as both a developer, administrator and consumer of APIs.

Faster development speeds. Unprecedented productivity. API-led connectivity to gain a competitive advantage. Enables developers to bridge applications together fast and hassle-free, allowing them to exchange data easily. The Mule run-time engine of Anypoint Platform brings together the power of data and application integration across legacy systems and SaaS applications, with a quick path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.

When we started to develop in MuleSoft, we need change our vision about the integration processes oriented to Web Services. You need to use other concepts and best practices, but they offer a great information about it in his blog.
MuleSoft is a great application like ESB (on-premise and CloudHub). When you have experience with it, develop is fast, controlled and easy.
A great characteristic of it, is the big amount of free connectors that it offers. You can connect with a great number of Internet service providers (through APIs).
The UI in the first steps could be complex, but, for this reason, is a great UI that has controlled all aspects of the development.

Server startup is really quicker than all other integration tools i have experienced. VM queue is awesome feature enabling messaging without a server in between. Object store and Cache is also an excellent concept. I would like to avoid cluttering the code with all the logs we had to add in the code in order to trace a message flow.

ease of of use ,anyone can use it, even u dont have much technical knowledge

Using Anypoint Studio in my day-to-day work for integrations, I've found that Anypoint studio makes creating simple integrations very easy to do. However, once we get into more complicated integrations, Anypoint starts to get a little less usable with just the out-of-the-box features. At least they make it fairly simple to add custom processes.

This is great upgrade to SOA approach, implemented as it is envisioned i.e. API led conectivity is the wave of future.

I have used the Anypoint Platform to create a Multi Protocol Messaging Platform (using SMPP and SMTP). Harnessing the capability to design, run and deploy all in one platform, I have shortened my development timeline (and probably my headache) from an estimated two years to almost 6 months.

The pros:
* Flexible - In terms of what solutions you can do, from Automating event-driven services to
orchestrating various exposed APIs.
* Well Adapted by the Community - There are lots and lots of tutorials that will let you in on the "How-to's", ranging from videos, blog posts, forums and knowledge sharing sites (im looking at you, stackoverflow)
*Very Powerful - Even using the base building blocks/components of the Anypoint Platform you can certainly do a lot, Simple Automatation, Complex chaining of API calls (and gather them back as one neat result) Capture and Filtering reports, Gather and Analysing data from logs..most especially given the rise of the IoT or Internet of Things. You can even build your own custom components to leverage the capability of the platform.

The cons:
* Steep Learning Curve - Coming from a web development background, it has a lot of settings that may or may not break your application. It will take practice before you can successfully say that you have an optimum working application. But this gripe comes from a 7 year PHP based developer with little to none experience in developing applications using Java. :)