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.

We primarily use the solution for integration purposes. 

The solution offers good policies. We have all the policies available via drag and drop. It made it very easy.

I don't have any notes for improvements. I'm happy with it. 

I'd like more monitoring and analyzing features included in the future. It would be helpful to have a dashboard with monitoring and health check visible to users. 

I've used the solution for two years. 

The solution is stable. I'd rate it ten out of ten. There are no bugs or glitches, and it doesn't crash or freeze. 

I'd rate the scalability ten out of ten. It is easy to extend. We have multiple users on the solution. We have around 100 users so far. 

I don't have any experience with technical support. I cannot speak to how helpful or responsive they are. 

I've also used Apigee, IBM API Connect, and Kong Enterprise. They are pretty new for me. I've used Apigee and IBM for a couple of weeks. I did not use a different solution previously.

The solution is pretty easy to set up. I'd rate the ease of setup ten out of ten. That said, I was not involved in the initial deployment directly.

I'm not sure about the solution's pricing. 

Currently, I'm evaluating the difference between this solution and Apigee, IBM API Connect, and Kong Enterprise.

I'm a customer and end-user. 

This is a very useful product. However, it is involved, and you do have to learn a few things to use it effectively. 

I'd rate the solution ten out of ten. 

We are a user and a consultant for MuleSoft. We provide integration services, including legacy modernization and application modernizations. Integration is one of the core aspects of web services. 

We provide modernization services to customers by moving their legacy apps to a modern digital-first, API-first architecture. Our aim is to provide business agility for the introduction of new products and services and to reduce costs associated with legacy application integration.

Leveraging MuleSoft's Anypoint Platform allows us to seamlessly integrate across different systems within enterprises, enabling customers to extend their products and services to the market with seamless channel integration.

Key features of MuleSoft API Manager include connectors capabilities for seamless integration with Salesforce and ERP systems, ease of API management and security, configuration-driven management, a dashboard for API traffic monitoring, insights for API usage, and ease of development.

The roadmap could include more GenAI use cases integrated into the platform, focusing on various industry verticals. Additionally, there should be capabilities for running GenAI models at the edge, bringing data to edge devices without compromising security.

We started with AditcourSes Evolve and Tuxedos Evolve for strong ESB-based integrations and moved to the current solution due to the flexibility and connector availability provided by MuleSoft.

We provide professional services as part of our offerings which include consulting and advisory services.

MuleSoft API Manager offers a competitive SaaS-based pricing model, usually depending on the deployment option chosen by the customer.

In addition to MuleSoft, we have used solutions like Kong Gateway, Boomi iPaaS, and Check Point integration products.

We have an evaluation framework for various platforms. The decision between MuleSoft and Kong often comes down to customer preferences and their existing ecosystem investments.

I'd rate the solution nine out of ten.

We primarily use the solution for API management.

Their gateway is great. They have a pay manager gateway which I find very interesting. 

We like their API manager.

Their RTF, runtime fabric, is very useful.

The stability overall has been pretty great.

We didn't have any issues with the initial setup.

Technical support has been very helpful.

Their ability to observe is good.

Some items are not ideal. For example, they should for sales management, they need better performance in the core processing.

The IO blocking isn't ideal.

We find that the enterprise level is lacking scalability.

We have some hundred Linux boxes and 400 or so APIs and for scaling, we are facing challenges. However, we haven't yet compared it to other ESBs, and therefore it's possible that all ESBs are limited in the same way.

They're in the process of evolving right now. There are many changes on the horizon that may prove to be interesting. For example, we've implemented CI/CD and now it's my understanding that the graph scale's also coming. 

I've been using the solution for four years.

The stability of the solution is pretty good. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

The scalability is lacking. We're not sure if it's just this solution or ESBs in general, however, we've had trouble scaling as we need to.

We have about 100 users on the solution currently. They are mostly tech leads, senior developers, and architects.

Technical support has been great. If you raise a ticket, then they respond on the basis of the severity of the issue, the criticality of the issue. They attend to the call really quickly. We've been happy with the level of support on offer.

The initial setup is very straightforward. We didn't have any issues at all. It's simple and easy to implement and not overly complex.

We have 30 to 50 people that comprise a support team that can help handle any maintenance issues. 

We did have assistance from MuleSoft support.

I don't have any visibility on the licensing and therefore cannot speak to the exact cost of the product.

We are working with a platinum tier and have an unlimited core. It's my understanding is that there are no additional costs beyond the licensing fee itself. 

We've gone live with MuleSoft and I have been comparing it with TIBCO or Dell and IBM products. If it's threat management that can be done concurrently across platforms, maybe it can be performed better. However, I've heard TIBCO is not evolving at this time.

I was exploring other options for my own knowledge and understanding as I am looking for a job change. People not only use Mulesoft, and companies want to have knowledge in two to three platforms. I'm just comparing Mulesoft with IBM ESB, Oracle, and a few other products. 

We're just a customer and an end-user.

Previously, a Mulesoft community edition was available. We started using Mulesoft's community version. We were exploring some ESB in our organization four years back. We started using MuleSoft as we've got Salesforce. At that time, Mulesoft was not yet acquired by Salesforce and that's why we went with the community edition. It was good. It was free. Then, slowly, we purchased some courses and Mulesoft was more connected to Salesforce. Now also Salesforce is there and AWS is there and it's more well-known and integrated. We thought it would help us due to its growth.

I'd rate the solution at a seven out of ten. It's a product that's still evolving. 

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.

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 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.

We are using the solution to move away from a point-to-point integration to a more managed API platform while doing analytics to monetize the API. We use the solution daily.

When doing point-to-point integration, you would need to set up the VPN and Exchange, but it is now easy because once you define an API, you can quickly expose it to third parties. Since you do not need to redo the work, the time to market is faster. In terms of analytics, you can read the traffic rating and even the monetization.

The auto-creation of the API documentation is useful. I used RAML for that, and it made creating API catalogs easier. The solution automatically creates API documentation based on how you define it.

The solution is missing a monetization module. One of our key use cases is engaging with third parties, so the solution has a disadvantage because you are forced to enter a contract with another third party just for billing.

Moreover, there are readily-available connectors, such as Oracle E-Business Suite, but you will have to pay for that. In that way, the solution might get expensive. These connectors should be easily accessible from the marketplace once you have access to the platform, rather than them reselling other products to you. It now defeats the whole purpose of quickly integrating a finance platform without further costs, and you are then forced to redo an already available connector if the budget does not allow you to purchase that connector.

We are still in the initial stages but have been developing APIs on MuleSoft Anypoint API Manager for roughly three to four months.

I rate the stability a ten out of ten because there have not been any issues so far. I am confident we can add more APIs.

I rate the solution's scalability a nine out of ten. We have 20 developers at our organization using the solution, and we hope to increase that number because we are roping in other developers from our SPUs to onboard them onto the platform.

The vendor trained us and offered support beyond the contract, so I rate their after-sales support positively.

Positive

I rate the initial setup an eight out of ten. It is straightforward, and deploying the solution took a week or two.

MuleSoft technicians trained and then assessed us on the solution as a part of the deployment process. The solution architect then monitored us until we could deploy the solution on our own. There were some APIs that they deployed themselves, and we started onboarding our own APIs once we were ready to do so.

During deployment, we required one person for the networks and one for the connectivity, and we also needed a solution architect. We had one person designing the architecture and one for development.

We only need one developer/administrator for maintenance, but maintenance is not an issue if you are used to the solution.

I rate the solution a seven out of ten since it is expensive from a Zimbabwean perspective. There are no additional costs apart from the licensing costs.

The solution is highly rated and is in the top three in Gartner Reports, and I highly recommend it. I rate the solution an eight out of ten.