MuleSoft API Manager Reviews

We use the solution to do buy-in alignment. There's a banking industry framework that tries to create the bank of the future. There are hundreds of different functions and business domains within a big bank or a small credit union.

The goal is to align reusable process APIs to that framework and then tie them back to system APIs that decouple your systems of record. It's a huge program to resurface credit unions and banks completely using APIs.

I was pleasantly surprised in a couple of places. The solution has a feature called Flex, which is a low-latency API layer for passthrough APIs where you want data mapping but with very low latency and high scalability. That was quite a surprise. The second was having an API catalog that could feed everything as first-class citizens.

You could have a Swagger File, a GraphQL query schema, a socket, an async API, or data mappings. Being able to catalog a bunch of related integration artifacts for reuse and get feedback seemed very effective to me.

It's pretty cryptic for a new user to learn the ropes and do basic things. The solution could be improved in educational and onboarding areas.

I have been using MuleSoft API Manager for three weeks.

I spent my first 20 years at the big three banks, Bank of America, Chase, and Citibank. Thousands of people used the solution in those places. Around 200 to 300 people are directly using the solution in my current organization.

You can instantiate Java-based GraphQL, orchestration and data mapping, or Envoy-based Flex Gateways. The Flex Gateway provides high throughput and scalability, but it's meant for a very focused use case. The ESB Java-based features are very flexible, but they're still pretty scalable.

One unique thing about MuleSoft API Manager compared to Azure is that it has all the components within that ESP. Azure API management makes you call out to other islands within the Microsoft ecosystem. The architecture leads to better scalability and availability with the MuleSoft API Manager approach.

My goal is to create a world-class API. I'm trying to achieve things like end-to-end traceability, observability, strong authentication, or granular authorization. The documentation does not clearly explain how to scaffold and automate the full set of reusable use cases.

If you carefully analyze it, the solution's pricing will be the same as other tools. The solution looks more expensive on the surface because it builds all the functions into one core component or into an integrated suite of components. You get a richer set of full life cycle tooling. You're paying upfront for the scalability.

If you use a cloud like Azure, you send transactions to multiple different services, eventually totaling up to a similar amount of money. However, you'd be locked into one cloud provider with that approach instead of being multi-cloud.

I would recommend the solution to other users. In the last few weeks, I've learned so much that I didn't know existed. I see the solution's holistic benefits, especially for people revamping most of their company's API ecosystem. The solution does present some compelling benefits.

Overall, I rate the solution an eight out of ten.

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.

I think that they can bring some transparency in reference to the terms of the microservices architecture. It is already there, but it is not obvious. 

I have been working with Mulesoft Anypoint API Manager for the past seven to eight years.

We have not seen many tickets which tells us it is very stable.

Everything is on the cloud and it is very scalable. We have around one thousand five hundred users onboard.

I think that technical support is good. They are coming out with a community edition as well as an enterprise edition. If you have full enterprise support, they are pretty responsive. 

Positive

The setup was great. Depending upon the size of the program, and the number of integrations that you are having, you will keep on adding the people based on the business requirement.

If you have a strong engineering background and capability, then you can setup everything into automation where you can have three processes. When the pipeline is setup, then the deployment can be easy. They call a C4E Center for Enablement, which helps in terms of setting up the right practices, platform, governance, and best practices.

I think that it is pretty expensive. It is very innovative in terms of multiple licensing options out there. So, depending upon the need of the organization, they can offer different kinds of licensing. 

I would rate Mulesoft Anypoint API Manager a nine out of ten.

We use the solution for process orchestration. We have some upstream and downstream systems, and the orchestration happens there with the help of MuleSoft Anypoint API Manager.

MuleSoft Anypoint API Manager is a low-code product. You can build an API with Python or Java as well. Since it's a low-code tool, you can easily develop an API and expose it to the consumers. The solution's data view coding language is easier to use than other languages.

The solution should facilitate the creation of custom connectors for use cases where a user would require extra connectors. This will make it easier for the user to use the product.

I haven't suffered many breakdowns or security issues with the solution. Nowadays, we are using CloudHub. However, we faced some stability issues when we previously used RTF (Runtime Fabric).

MuleSoft Anypoint API Manager is a scalable solution. More than 50 people use the tool in our organization.

The solution’s initial setup is easy.

MuleSoft Anypoint API Manager is an expensive solution.

I would recommend the solution to other users because it is easy to use. However, users should first consider the solution's high license cost. Depending on the execution, the solution is worth the money. New users will find the solution easy to use.

Overall, I rate the solution an eight out of ten.

We could employ it for tasks like access control and other minor functions like controlling licenses using an API gateway alongside SS rules.

It is a good management tool for controlling purposes.

Since most components are situated in the cloud, there's one particular hosted in the cloud. This presents a considerable challenge. While all other components are implemented on-premises, this specific one isn't permitted to be hosted in the cloud as per customer requirements. Shifting this component to an on-premises environment requires a significant effort. 

I have been using MuleSoft Anypoint API Manager for more than two years.

It is a stable product. 

Regarding scalability, I have some uncertainty. During our interaction with the vendor, they introduced us to the possibility of running MuleSoft within a Kubernetes environment. If we can leverage this approach, it could potentially enhance scalability. However, during the testing phase, I found that the implementation process was rather complex.

I would rate the scalability seven out of ten.

The support is satisfactory.

Neutral

It is complicated. I would rate it three out of ten. We collaborated with professional service experts based in Hong Kong. When delving into the architectural aspects, it became apparent that the setup was intricate. Consequently, we relied on their assistance for both the installation process and the architectural design. The project itself extended over a considerable duration, not solely due to its length but also because it involved multiple components.

It is extremely high, and I would rate it one out of ten.

Personally, I find this to be a satisfactory option. I would rate the product seven out of ten.

Our primary use case for the solution is managing all the new APIs, and we deploy the solution on cloud.

We were trying to integrate, and we were trying to expose ourselves to external B2B scenarios. So we exposed our APIs overall and new API management. We found it easy to configure partners. It also allows us to create a new client secret, providing access limits, rate limits and more by splitting it into multiple tiers of services.

The integration of API management with security features is valuable. For example, communication security is very strong, and it automatically decrypts your images and encrypts your messages during communication. In addition, it provides different kinds of policies you can apply, which is just a plug-and-play configurable, which is very easy.

Monetization and cataloging can be improved. So we are looking for monetization to understand how well we can catalogue.

We have been using the solution for approximately four years and are currently using the latest version.

The solution is stable.

The solution is scalable. Currently, all our developers use API Manager.

We have had a good experience with customer service and support. I rate them ten out of ten.

The initial setup was straightforward.

We implemented the solution with an in-house team.

We have seen a return on investment.

I rate the solution eight out of ten. I advise new users to ensure they are configuring security as it is the most important key to success.

I use the solution in my company because we are looking at synchronizing all the messages that come into our trading platform. We are also looking at various applications and feeding points, and MuleSoft has been helpful for us. Essentially, the use case is attached to stock broking.

The most valuable features of the solution are the low code environment, the drag-and-drop functionality, and the ability to drop the connectors on the fly, which are extremely helpful.

There are some loopholes in the security policies that could be improved.

The tool's robustness ensures who can access the platform. If there is a cracked version, the tool can track that. MuleSoft Anypoint API Manager needs to watch out for compromised licenses.

I have been using MuleSoft Anypoint API Manager for two years and three months. My company serves as an implementer of the product.

Stability-wise, I rate the solution a seven out of ten.

Scalability-wise, I rate the solution a seven out of ten.

My company's clients are medium-sized businesses.

I rate the technical support an eight out of ten.

Positive

If one means difficult setup process and ten means easy setup phase, I rate the initial setup of the solution as an eight.

The solution is deployed on the hybrid cloud model.

The solution's deployment took our company a few days only because of the vendor and client policies.

I think that the return on investment is fairly okay. I don't have the numbers to speak about the ROI because the people involved in the business part look into it. I have done just a small level implementation of the product. I don't have access to those numbers as the business heads have driven the solutions in our company.

If one is cheap and ten is expensive, I rate the product price as six and a half to seven.

The security policies in MuleSoft Anypoint API Manager are helpful. It is a pretty neat platform.

The use of the product for AI-driven projects has been fairly okay.

I would recommend the product to others who plan to use it, considering the ease of use that it offers, along with the help or support that is available for users.

I rate the tool an eight out of ten.

I have dealt with a few use cases involving MuleSoft Anypoint API Manager, but I am unsure whether its features are useful in my company. The tool is useful for the governance of APIs that I have created with some policies, like SLA-based policies or rate-limiting policies. In general, it is an advanced product.

The main reason for using MuleSoft Anypoint API Manager is that the company's external systems inside the customers' ecosystem need to be publicly called APIs by providing the paid version of API so that anyone can access the endpoints from the internet. In our company, we need some tools to configure who can or can't call you while being able to control the amount of calls, irrespective of how many they are. In our company, the tool becomes useful to make five calls per minute with our current license.

The most valuable features of the solution for securing APIs stem from the tool's ability to allow users to deploy policies.

The tool already can solve the problems for which it was designed, and it is really hard to have any thoughts over what can be improved in the product, as it is a very niche task.

The product's price should be available for public review since it is not currently available for others to see, making it one of the areas where the product has certain shortcomings. The product's price is revealed only when you contact MuleSoft Anypoint.

I have experience with MuleSoft Anypoint API Manager for a year.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

My company deals with clients having small and medium businesses.

I rate the technical support a nine out of ten.

Positive

I rate the product's initial setup phase a nine out of ten.

Experienced developers can deploy the product in a day.

The product is expensive.

Speaking about how MuleSoft Anypoint API Manager helps in the area of API lifecycle management, I would say that API Manager can be considered the last step after you have established all your systems in your environment. It is useful to configure some small details in areas like rate limiting.

The monitoring part of the tool is not needed for simple solutions. The monitoring part of the tool is required when you have a large ecosystem of different software applications. The tool helps monitor when your systems slow down. I don't have experience with the tool's monitoring part.

The benefit of the policy management feature in MuleSoft Anypoint API Manager ensures that your APIs are secured. The tool also provides our company with very flexible control when it comes to the usage by our clients.

I rate MuleSoft Anypoint API Manager's support for my organization's digital transformation efforts a ten out of ten.

I have no special recommendations for those who plan to use the product. The tool is used by technical developers for development purposes.

I rate the overall tool a nine out of ten.

The use cases are regarding telecommunication provisioning. Another aspect involves managing logistics, which includes connecting suppliers and the company's partners.

MuleSoft Anypoint API Manager is initially complex to utilize, but it provides extensive control over various capabilities. This means it can create high-cost solutions, allowing for a great deal of customization to make it well-suited for specific needs.   

When discussing potential enhancements overall, it primarily involves making it more user-friendly and lowering the pricing. There are several aspects that could benefit from improvement, or perhaps a few other areas to consider.

I have been using MuleSoft Anypoint API Manager for the past five years.

It is stable and has no problems. 

It is scalable and appropriate for every enterprise.

I have no experience with tech support.

The ease of maintenance depends on how you design your solution. You should consider having a team, typically consisting of four or five members for maintenance.

Comparing Mulesoft with Microsoft, MuleSoft has an advantage in the sense that it offers an all-in-one solution, while with Microsoft, it's more like dealing with numerous separate components. So, you have to figure out which specific components you need and how to connect them, almost like a toolkit that provides options to connect and integrate different things. It can be a bit challenging to determine which one is the most suitable for your needs in Microsoft's case. While you can build nearly anything with it, there's always a search for better methods to achieve your goals.

When considering the adoption of MuleSoft, it's important to take into account the expenses, including the licensing costs and the time and costs associated with training to become proficient in using it. On the other hand, starting with Azure might offer a more straightforward path to expansion and growth.