MuleSoft API Manager Reviews

We are using MuleSoft API Manager in our organization. Currently, we also have Azure API management gateways in use. However, due to cost considerations, we are more inclined towards Azure API M but continue to use MuleSoft API Manager as well.

The MuleSoft Exchange and the Experience Hub stand out as the most valuable features. They provide a smooth and straightforward process for creating and building integrations, especially when compared to other API gateways. 

Additionally, MuleSoft's ability to connect to third-party monitoring platforms like AWS, Datadog, and Elastic makes operational analysis more efficient.

We primarily use the solution for our APIs. We are moving from monoliths to API architecture and we have approximately 10,000 to 12,000 APIs across banks, which are hosted on this product. It also provides us a gateway service to ingress the traffic as well as whole policy management where stuff is taken care of from the PC Any Point. It also has some API-level runtime policy management, which we use.

The gateway service to ingress the traffic is great. 

The whole policy management has been great. 

It has some API-level runtime policy management, which is useful for us.

The solution is extremely mature.

You can scale the solution.

Our primary use case for MuleSoft API Manager is to manage APIs and publish APIs so that whoever is the consumer can understand and access the API specifications on the exchange. 

They can build their codes based on those specifications when calling or consuming our APIs or pushing data to our APIs. It is also used for testing purposes, as API Manager provides stubs for initial testing, which helps consumers.

The MuleSoft API Manager has facilitated the management and publication of APIs, enhancing efficiency by providing clear API specifications for consumers. Its testing stubs also aid in initial testing, improving the overall development and integration process.

Our company used MuleSoft API Manager when upgrading to a new SAP S/4 system. We created many APIs following the API-led architecture, building system APIs, processing APIs with our logic, and exposing these to other systems.

I found the authentication features very valuable, like how the tool provides client IDs and secrets and lets you apply authentication policies. We bought the Titanium package with analytics, which allowed us to do rate limiting and throttling. The API monitoring and alerting were also useful.

The API analytics feature helped with our three-layer architecture. When debugging, we could track payloads across the three API levels using correlation IDs, which was very useful.

MuleSoft API Manager helped us overcome several challenges. Before, we didn't have good authentication policies and had to depend heavily on our DevOps team. With the tool, developers can manage everything end-to-end after setting up CICD with DevOps. This was a big advantage as we no longer needed to involve the DevOps or security team to look into security or policies for every application deployment. Having the most control within the team saved many people's time and effort.

We do business with a lot of other vendors and customers. Our main core business is to lend loans and lease furniture. In this context, we have to create partners and we have to do multiple transactions with multiple vendors and multiple facilitators. In this venture, we consider APIs the best, and our most sophisticated medium to communicate with other partners and other lenders at home and elsewhere.

We want APIs to be the most sophisticated and more robust. REST APIs are the core in this area. We have been using Mulesoft specifically to create our REST APIs, enlarge them, and also expose the endpoints to our vendors so that they can use them. Internally, we have been using the APIs extensively for all of our internal application communication. Raw ping and workflow and all those things. We use this Mulesoft extensively for API management, REST API stack, and also for the workflow.

We're going to have a task with another bank who will be lending us the loan or they will be giving us some money for us so that we can lend this to double customers and expand into different industries. We're doing the business directly with those banks who we're really trying to work with, and doing joint collaboration so that we can lend loans to the customers, the retail customers.

In this context, we have to collaborate with those banks in a sophisticated way. Few banks are very, very advanced in the necessary technology. We propose of them usage of the APIs. The advanced banks already have the APIs. That kind is a very smooth transition, but the banks whom we're working with, a couple of small banks, don't have the API stack. Whatever the legal systems they have, we enforce them to convert those existing legacy systems as the APIs, and also those other REST APIs, and we can have a smooth transition.

The initiative went very well, and they're very happy with a lot of the tasks we have been doing. Now, they have extended the business. They want to censor their existing systems. They want to expand their system. This is one of the examples of how the solution has improved our organization. In this juncture, we place Mulesoft as one of the core solutions in our organization API stack. Communicating with one application and other application, or the validation of the loan ID or the validation of a customer or generating the customer base, whatever it is. For the day to day tasks, we use API systems only. API is one of the most crucial parts of the IT initiatives which are going down in our office on a day to day business.

Our primary use case is API connectivity when integrating different systems or applications with the help of the API. There is a very robust API architecture that helps in directing different applications. In the B2B space, they have come up with a new offering, which is a partner manager, that helps to have the B2B integration with any EDI, X12, or any other B2B transactions. 

I believe the API connectivity within the cloud marketplace is most valuable. There are a lot of services available in the form of services or microservices, which are exposed via the API. Currently, API connectivity has become a mainstream integration. When you go to the B2B space where they have the partner ecosystem, there are a lot of suppliers and vendors there. Integrating them seamlessly for your supply chain or for your inventory management creates an efficient team of partners.

We worked predominantly for the BFSI financial sectors and for one of the automobile industries. They're taught in Europe. 

The applications where the customers wanted to download a report, a customer is associated with multiple customers, where they wanted to download the reports for analytics or just wanted to see what is the annual income or something like that. We expose an API for each customer. We will apply a policy where the APIs are being secured. So, each customer will have their own client ID and client secrets.

It has improved a lot in terms of monetizing your API. You get a benefit out of it, and then you secure your API. You restrict the external threats, managing the API end-to-end and governing it. All the features are pretty cool.

We use MuleSoft API Manager effectively to manage traffic, especially in scenarios where we need to control access to sensitive data for public bodies. By implementing the API gateway, we ensure traffic control and enhance security for personal data APIs. This solution provides a layer of control and security without changing our existing technology stack. It also helps in managing traffic for mobile applications, ensuring seamless consumption of our services while applying necessary policies for governance.

The most effective features of Anypoint API Manager for policy enforcement include security enforcement, rate limiting, client enforcement, traffic control, service level agreement policies, and caching policies. These features provide a comprehensive set of tools to ensure governance and security across our APIs, enabling us to meet the diverse needs of our clients effectively.