What advice do you have for others considering Mulesoft Anypoint API Manager?

Depending on the client's requirement, MuleSoft is recommended if a comprehensive integration solution is needed, including API management, transformation, interface building, and proxy creation. However, if only an API management platform is needed, other solutions like Apigee or Azure API may be more cost-effective. I'd rate the solution seven out of ten.

I rate the overall solution a nine out of ten.

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.

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.

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.

I would definitely recommend it. It's a fantastic product. Overall, I would rate it a nine out of ten.

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. Overall I would rate it an eight out of 10.

I advise customers to build a strong technical and integration design team. MuleSoft Anypoint API Manager is a strong product and provides services beyond API management. It is ideal for large companies. It could offer packages for small businesses as well. I rate it an eight out of ten.

Both the cloud and on-premises options are available. Customers can leverage the MuleSoft Cloud platform to deploy the applications or set up their own online infrastructure to deploy applications. There is another solution available that can be used to leverage some of the other cloud platforms, like Azure, CCP, or AWS. This can be used to integrate with cloud platforms so that applications can be deployed. I would advise customers that instead of building their infrastructure from scratch, they should choose MuleSoft Anypoint API. I would rate the solution an eight out of ten due to some scalability and pricing issues.

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.

I would rate the solution a nine out of ten. AWS is cheaper than MuleSoft.

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.

Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I work as a tech lead. My company is a MuleSoft Anypoint API Manager customer. About ten people from different departments take care of the deployment and maintenance of MuleSoft Anypoint API Manager. I'd tell others planning to implement MuleSoft Anypoint API Manager that scaling the solution can be costly. Hence, it's essential to factor in the costs. I'd also tell others that MuleSoft Anypoint API Manager is easy to use. Still, as a solution, it would benefit more from improved DevOps to make it even easier for users and result in more business for MuleSoft. I'm rating the solution eight out of ten because it's easier to run and manage than others.

We're trying to build a partnership with MuleSoft right now. I'd rate the solution nine out of ten.

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 would rate Mulesoft Anypoint API Manager a nine out of ten.

I rate Mulesoft Anypoint API Manager a seven out of ten.

You will need to look at your requirements and choose the solution. Message Broker, ACE only has ESB and does not have the gateway. You will have to buy additional software, but MuleSoft has embedded both API and ESB. This is called method-oriented architecture. In terms of the speed and process, I prefer Message Broker, ACE technology IIB. In my current project, we are processing 25 MB to 50 MB files, and Message Broker is able to do it. However, with MuleSoft it would take more time. MuleSoft has advanced features but is slower. I would rate Mulesoft Anypoint API Manager at ten on a scale from one to ten.

I would give Anypoint API Manager a rating of nine out of ten.

If your organization wants to build reusable functionality using APIs and you are a cloud-first organization, I would recommend MuleSoft. I would not recommend this solution for tactical integrations but rather for strategic investments. You need to have a long-term vision as to what you are building, where you are building, and how best you can reuse what you build across the enterprise. I would rate this solution an eight out of ten.

Anyone planning to use this product should invest in some training beforehand. I rate this solution eight out of 10.

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.

I'd rate the solution at an eight out of ten. It's good. I've enjoyed using it. I would recommend the solution to others. It's a good platform.

I'm not sure I would recommend the solution to everyone. The approach we have taken is, we have moved out completely from the Mule APIs to Spring Boot APIs. We will decouple the whole vendor locking and stuff. However, it depends on the use case for each company. There is no good and bad product. These guys are both very mature products. Depending upon the use case, you will have to consider how you will handle scaling, for example, or other challenges. Everything has a drawback and plus and minus, so pros and cons. Even Kong is a new product. It may be a good performer, and very lightweight, with low infrastructure needs. We don't know. Our cyber is very strong. Like us, people will have to evaluate, depending upon their use cases, all the pros and cons of security and see how it fits. I'd rate the solution at a seven out of ten.

In our work, we carry out a deeper analysis of customer requirements. Based on their fixed rate product capabilities, the size of the organization, and the business case, we carry out an evaluation and propose a unique solution. We have our own evaluation process, which is quite extensive and includes architect scalability of configuration, maintainability, and then commercial licensing. Taking into account all those parameters we can figure out the best possible solution. It really depends on what the customer needs. I rate this solution a nine out of 10.

MuleSoft has both ESB as well as the API management platform. We are implementors. We are one major version behind. We are not using the latest version of the solution. We deploy on-prem and we also have deployment on our own AWS OSSIE code infrastructure. It might be cheaper for someone to implement MuleSoft on-prem rather than on the cloud. With the on-prem version, we can deploy as many applications as we want on the on-prem version, provided the infrastructure is able to support it. However, for cloud-based deployments, they end up charging more. I'd rate the solution at a nine out of ten.

I would rate this solution an eight out of ten.

I would rate Mulesoft an eight out of ten. Not a ten because of the pricing. I would recommend it.

I would rate this solution a seven out of ten.

My advice to anybody who is considering this solution is to first make sure that there are no alternatives that are most cost-effective, such as open-source products. Many of them are much cheaper but are still able to provide the same relevant functionality and the same level of data security. I would say that MuleSoft has the best API manager but it is not the cheapest one and as such, not for everybody. It is not everyone who needs to connect expensive systems together. I would rate this solution a nine out of ten.

Frankly speaking, I don't think that Mulesoft is doing an extremely good job. It may be because it's not that easy to satisfy me from an API point of view, whether in development, maintenance, or management. I have been working in this area for quite a long time and my standards are a little bit high. That said, this is a competitive market and I understand that it is not easy to make a good product. I would rate this solution a seven out of ten.

The advice I would give is that this is a platform that's meant for a complete digital transformation of an organization. If you want to realize the entire capacity or the entire power of the platform with the capability APIs and the system APIs, you know you've got to use the API-led connectivity. And here I think lies the true power of the platform; that instead of using it just as an API gateway, you can take it further and I think that is the real value that market peers are not able to offer. It's a standout feature of the API platform and MuleSoft. I make proposals and whether the customer chooses it or not is up to them. I usually look at different products, and then we try and see what fits the customer best. It's not black or white. If there is a need for an entire landscape of low APIs and not just proxies, I think MuleSoft is a good way to go. I would rate this product an eight out of 10.

I'd rate the solution nine out of ten. Mainly the pricing is the big down-side of the solution. I'd advise others to ensure that they need to have the right partner who understands the system before they get into the implementation process.

This is a good solution but nothing is perfect and there is always room for improvement. I would rate this solution an eight out of ten.

There are a lot of products available on the market. Mulesoft is very good. It's an amazing product, no doubt about it. There's quality in the standard version, and the acumen and the technology are very good. What I want to tell them is before going for Mulesoft to consider Apigee. There are a couple of open-sources out there. What I would suggest is to not go blindly with the product stack. If you want to use the APIs, understanding of APIs are must because no company is independent. They have to do business with other companies. API is one of the most standard and robust methodologies to communicate with other business and do the business for the day to day transactions. And API is one of the most friendly approaches. In this juncture, before going with an API management solution, understand whether you can create your own in-house APIs and see if you can leverage on that based on for the timelines and the costs. Then you can examine your goals because not every company is the same. Product due diligence is must especially when you do business with huge numbers of customers. For those kinds of numbers, you have to do an aggressive and some scale due diligence before going for the product. My suggestion is to do due diligence and find the registered products, which are capable, and customizable for your requirements. Then you go with that product. As far as Mulesoft is concerned, yes, most of the small-scale and medium-scale customers, yes, it is one of the best tools. But when you scale up for large-scale customers, it has got those capabilities, but the Mulesoft team is not addressing those capabilities. With Apigee, they address the concern and they go after a solution, and have a different approach, whereas, with Mulesoft, they insist the customers follow their methodology, which may or may not be suitable for all the lines of businesses. But when you come to the Apigee, they tailor to vendors, they customize themselves and act as the business owner, and they make for the business one of the best solutions. That's the difference. However, I'm sure that what Apigee can do, Mulesoft can do better. But they have to address these concerns. To address these concerns, they should publish more articles, and the tutorials should be updated. The tutorials and the knowledge base should be updated thoroughly, and it should be made available for all the customers, as well as new learners. Generally, they can make their product more sellable. It should not be hidden. I feel that is one of the challenges they have been facing, and they're not addressing that over a period of time. I would rate this solution at 8 or 8.5 out of 10.