MuleSoft Anypoint Platform Reviews

I am involved in architectural design using MuleSoft Anypoint Platform.

The most valuable feature for me is the Exchange sub-tool. It provides details about the APIs, such as availability and functionality. MuleSoft Anypoint Platform helps to standardize data integration approaches, making it easier to implement integration projects. Additionally, it has a lot of connectors out of the box with many products, which ease the integration process.

MuleSoft Anypoint Platform is a kind of API platform. We use it to manage and maintain our APIs in terms of content capabilities, monitoring, and as a gateway. It allows deploying applications into runtime, integrating with data, and building code around data integration.

MuleSoft Anypoint Platform provides various capabilities for managing APIs, including deploying applications into runtime with seamless integration with data. It allows for imposing security policies, mock testing, and tracking transactions. The platform is integrated with Salesforce, making it preferable when using Salesforce products. 

Additionally, it reduces manual loads in maintaining servers as it comes with the Cloud Hub feature.

We primarily use MuleSoft for integrations and API management. This involves pragmatic usage of API-led connectivity and managing complex integrations.

The platform saves implementation time and offers clear visibility of integration assets, which is crucial for managing numerous integrations in large enterprises.

I can describe the use case for MuleSoft Anypoint Platform by explaining what processes people mostly use the product for.

MuleSoft Anypoint Platform can be recommended for all environments - small, medium, and enterprise-level - because they have the facilities and features which small enterprises need. Organizations need to evaluate based on the pricing since they have started with consumption-based pricing nowadays. The effectiveness of this model is still being determined as they are moving from vCore-based pricing to consumption-based pricing. This is something small, mid, and large enterprises need to consider.

The API-led connectivity approach of MuleSoft Anypoint Platform offers specific functionality based on various conditions.

They started with a strong go-to-market strategy. Currently, other integration tools have come up with ease of implementation. They also provide tools for citizen developers, which means they aim to reduce the technical knowledge required to implement integrations.

In MuleSoft Anypoint Platform, there is a disadvantage because users need substantial technical understanding, which creates a barrier for citizen developers. There is significant dependency on technical developers to implement solutions. This could be reduced by improving ease of development. They are working on this aspect, but it is not yet comparable to other tools.

So what we are trying to do is help a customer create a platform where they can integrate multiple business applications. Previously, they were using point-to-point integrations, but now they want to leverage Mule Anypoint Platform as the integration layer. They have about 60+ applications and close to 300+ endpoints that they want to connect through Mule. They are gradually migrating from SnapLogic and Workato, including data integration currently handled by Talent, to Mule as the unified platform. Our role is to assist in building these integrations. We are retrofitting some of the existing ones into Mule and ensuring a smooth transition from other integration solutions to MuleSoft. Additionally, for new businesses, they plan to build integrations directly on top of Mule Anypoint Platform.

In terms of improving our organisation, the first thing is cost management because there are a lot of licensing costs that people incur. There has been a significant improvement in business processes with a lot of increments because now, every integration request flows through the new platform. A 20% increase in all the connectivity from the enterprise applications. The shift from peer-to-peer or point-to-point integrations to Mule Anypoint Platform enabled this improvement.

Mule Anypoint Platform is used as an integration tool to integrate applications and for data transformations. It is mostly used as an integration tool to connect multiple systems, and it comes with pre-built connectors to allow users to connect with multiple systems, like SAP, Salesforce, or any of the message queuing systems, IBM MQ or Apache ActiveMQ. With Mule Anypoint Platform, connecting multiple systems, integrating them, and transferring data from one system to another is easy. The tool helps users have point-to-point connections and achieve an overall integration.

With Mule Anypoint Platform, there is a hybrid cloud deployment model, meaning you may have an on-premises environment or a MuleSoft-supported cloud platform called CloudHub. Users can deploy APIs using Mule Anypoint Platform, as it acts as a single point or place. Users can deploy the APIs from Mule Anypoint Platform to an on-premises environment or CloudHub. Mule Anypoint Platform integrates with CloudHub. In general, Mule Anypoint Platform helps to deploy the APIs and CloudHub. When we talk about the APIs, there are multiple policies one can apply on APIs, like rate limiting policies, OWASP policies, and OWASP security policies, that can be easily configured in Mule Anypoint Platform. Users can apply the policies via Mule Anypoint Platform and deploy the APIs to hybrid cloud deployment models, like on CloudHub, making the tool very helpful for users.

I use the solution in my company for API development and integration.

The most beneficial part of the product for API management tasks stems from the fact that it makes me capable of doing a lot of integrations and design patterns, including areas for regular integrations and ETL. The tool offers a very high performance and is very customizable, and my company didn't get into a complex task that we couldn't achieve with Mule Anypoint Platform. I am working with a very big organization where there are a lot of challenges, but till now, with the challenges my company has faced, we could face them in both areas, like management and API integration.

We performed a patient account integration between our CRM and our ERP. We were managing order integration between the systems. We also manage RMAs between the systems. We have an integration with a specialty pharmacy. We used the tool to capture account and order information from our external partners.

Using the solution was great. It was part of the project that we didn't worry that much about. What I also liked about it was that even though I'm not that technical, I could go in and look at thoughts and events and confirm that the information we were looking for was making it across. I could check at the interface level and lessen the burden on validation within the application.

The instrumentation within the solution is important. The ease of implementation is very important. Our partner development team had little trouble dealing with these diverse systems, with JSON on the one hand and SOAP on the other. The product’s ability to seamlessly translate protocols is great. The API-led connectivity is great.

The reason that we took on the product was that we wanted to learn about it. We wanted to figure out how to use it. A big payoff for this will be in EHR integrations. These systems are all alike, yet they are all different. They all use EPIC, and each installation is a little bit different. It’s a challenge when we go to different hospitals. MuleSoft has made a name for itself in using the integrations.