MuleSoft API Manager Reviews

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 primarily use the solution for API management.

We can use both on-premises and cloud setups. 

The API policies are great.

We can use command line, and it also has a good UI.

We can select the required servers and deploy API. It's great for managing the API.

If we talk about the designing of our API site with RAML and putting it into the exchange and then looking at it as a library, it's pretty good. 

The initial setup can be pretty straightforward. 

It's stable. 

We can scale the product.

I'd like an option for having customized policies also. I'd suggest that the product provide some inbuilt customized policies alongside the ability to fully customize.

The solution is expensive. 

They're coming up with lots of new things right now. I'm looking for something like AI-based monitoring in the future.

I've been using the solution for almost three years. 

The solution looks to be stable. It is reliable so far. there are no bugs or glitches, and it doesn't crash or freeze. 

We've found it to be a scalable product in general. 

I'm not sure of the exact amount of users. 

We have technical support from MuleSoft, and they have a portal where we can log the ticket. We've had a couple of resolutions already.

Positive

So far, we've had pretty straightforward setups. That said, we are looking to build a more complex project right now, and that implementation may be more involved. 

We were able to do a couple of things by ourselves. We are also planning on building a complex integration with the system soon.

I'm not sure of the exact cost of the solution. 

While I haven't had detailed discussions, my understanding is that the solution is expensive. I found it pricey when I was doing some research.

I evaluated a couple of tools. We wanted to compare to see what might be better. We wanted to use one of MuleSoft's business units. MuleSoft stands out.

We're trying to build a partnership with MuleSoft right now. 

I'd rate the solution nine out of ten.

We're using MuleSoft API Manager to integrate with an endpoint in our backend system to import much information into Salesforce. Other tools didn't allow for as many API calls, so we used it to create a new endpoint.

The tool needs to improve customization and interface. 

I have been using the product for a year. 

I rate the solution's scalability a nine out of ten. 

The technical support has been very responsive. I've opened three cases, and the previous ones were solved quickly.

Positive

I'm currently deploying MuleSoft API Manager, but it's not fully deployed. There have been some challenges, mainly related to IP restrictions, which I believe are on our side. The testing phase took about two months due to people being on holiday. I'm hoping the actual deployment will go quickly, but I'm unsure how long it might take as technical issues could arise.

I can't say definitively about cost savings since we're still in the testing phase. MuleSoft uses separate testing and production environments, with more resources allocated to production. So far, in testing, it works fine and does everything it needs to, but I'm not sure how performance will compare in production.

We faced IP restriction challenges, which we resolved by changing the authentication method from an API key. This solved the issue for now, but we'll need to verify it again in production.

Based on my 2-3 years of experience with MuleSoft products, I'd rate MuleSoft API Manager eight out of ten.

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.

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.

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. 

Our first primary use case for this solution are APIs based in MuleSoft. It's natural to use the MuleSoft API manager for MuleSoft APIs. We also use this solution's API manager to manage non-MuleSoft APIs in environments based on the MuleSoft platform. It functions as a kind of API gateway for us.

The feature I found most valuable is the ability to add a central place for managing your policies for APIs. This makes our life easier and enables central monitoring.

I would like to see MuleSoft expand the range of APIs you can manage with it beyond HTTP, GIPC, and others.

I have been using MuleSoft Anypoint API Manager for about six months.

I would rate the stability of this solution a 10, on a scale from one to 10, with one being the least stable, and 10 being the most stable.

My impression is that this product is quite scalable. I would rate its scalability an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I have not had any contact with their technical support team.

The initial setup was relatively easy. I would rate it a 10, on a scale from one to 10, with one being the hardest and 10 being the easiest. The deployment process was done with an in-house team of three people.

We have seen a return on investment but not from the product itself, but rather from the platform. If you adopt the whole platform, you can build composable applications. This will cut your time creating new applications and updating them – once you have everything running – by up to 50%.

I would rate the pricing of this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best. My opinion is that it's a bit expensive but they do offer a lot.

The advice I would give to anybody looking to try this product is: if you have a lab, test out all the MuleSoft features to make sure that they will bring what you need into your environment. I would say that with any product. It's always good to have a list of requirements and make sure that the product does what you want.

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.