MuleSoft API Manager Reviews

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. 

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.

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.

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.

Our primary use case is to consolidate server information about product stocks. We have data in different systems and offer an API to provide users with consolidated information. Our main system is SAP, and we use standard connectors to integrate it with Microsoft.

The most valuable feature has been the standard connectors, especially the integration with SAP. It was crucial for us since most of our information is stored in SAP, and accessing this data seamlessly was very beneficial.

The setup process could be simpler. We are still discovering some features, and simplifying the initial configuration would be helpful.

We have been using MuleSoft Anypoint API Manager for six months.

I rate the product stability an eight. While we have yet to encounter major issues, our experience is still limited, and we are in the discovery phase.

We still haven't contacted the support team directly. Initially, we conducted a proof of concept with our internal team, focusing on integrating with Microsoft products. Subsequently, we transitioned to working with the whole API team, who have found it easy to use.

The deployment model was cloud-based.

We implemented the product in-house.

It's too early to determine the exact ROI for the product as we are still in the initial stages of implementation and use.

The pricing is quite reasonable and affordable.

We evaluated Amazon API Gateway and Google's solution. After trying the proof of concept, we chose MuleSoft because our directors preferred it.

The integration process was straightforward. As the software manager overseeing our current IT workflow, integrating the product was a smooth experience. While we have only begun exploring its full potential, initial impressions suggest ease of use and usefulness. The configuration services were particularly seamless, contributing to our overall positive experience. Therefore, the integration process is easy rather than difficult. We conducted a proof of concept involving one of our developers and found the APIs provided by MuleSoft user-friendly.

Overall, it is a very intuitive and good product. It has proven to be effective for our use case so far. I rate it a nine 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.

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.

Overall, the platform is pretty good, I cannot say which one specific feature is good. The idea of an API Manager is really interesting.

One improvement is to add a plugin in the API Manager. If an organization is using SOAP services or legacy APIs. Maybe I don't want to migrate it to rest API, but my plugin should be able to convert Jason to XML. Basically, protocol transformation features in API Manager.

I have used it for over eight years as a service provider.

As for the stability, no issues up until now.

For scalability, our current licensing is for only ten APIs. Regarding the scalability part, haven't tested it yet.

We had some production issues, and we did escalate them. We got a good response from the customer support team.

It's cloud, so that's the pro. It has all the features that other API manager does, and there are some features that vary from product to product. Everything cannot be brought upon MuleSoft or Anypoint API Manager.  

Right now, the universal API Manager is applicable for any API hosted in any server, it is not only MuleSoft. If we can bring the feature, I am a customer who has a MuleSoft API, as well as an on-prem API, which is developed on Java or some other integration tool. Still, I wanted to leverage the API Manager capability to my non-mule APIs. If these kinds of features are provided to the customer, I think they should be very happy with that approach.

It is complex because it requires a lot of development effort and to understand the business. Additionally, it also requires an understanding of the requirement of how the API behaves. It should be very generic. So first, we can start off with SOAP services because the SOAP services accept only the XML. There should be some kind of configurations that you are plugging in the API Manager where you just define a scheme. This is just an idea where you have to define your scheme as in your platform API Manager and then define your SOAP services. API Manager will do a protocol transformation so we don't touch the existing applications. 

Many clients will also be attracted to this approach. The solution is deployed on the cloud. Deployment time depends on the deployment topology. In the cloud, it is pretty fast. We leverage the CICD framework for any deployment. It takes a maximum of a minute. One person can handle the deployment. There is no maintenance required for the product.

Our customers have a lot of concerns about the increased pricing. The customer feels MuleSoft is very costly, and they are also exploring other integration tools for a lower price. Maybe we should retain the existing customers by offering some discounts. At least the existing customers can be retained this way. This is regarding the licensing part only because customers based out of North America and Europe have shown many concerns recently. They are a bit concerned about pricing.

We help customers to build and manage an API. We help them to integrate their platforms and applications. I think a complete cloud setup gives a lot of flexibility. Customer need not worry about their environment or servers. The complete cloud setup has a 99.99% uptime. So, there is no downtime. I would recommend a complete cloud setup. Overall, I would rate MuleSoft Anypoint API Manager an eight and a half out of ten. That one and a half points will be dedicated because of some of the missing features, which I have seen from other API managers.

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.