Coming October 25: PeerSpot Awards will be announced! Learn more

MuleSoft Anypoint API Manager OverviewUNIXBusinessApplication

MuleSoft Anypoint API Manager is #3 ranked solution in top API Management tools. PeerSpot users give MuleSoft Anypoint API Manager an average rating of 8.2 out of 10. MuleSoft Anypoint API Manager is most commonly compared to Microsoft Azure API Management: MuleSoft Anypoint API Manager vs Microsoft Azure API Management. MuleSoft Anypoint API Manager is popular among the large enterprise segment, accounting for 75% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 20% of all views.
MuleSoft Anypoint API Manager Buyer's Guide

Download the MuleSoft Anypoint API Manager Buyer's Guide including reviews and more. Updated: September 2022

What is MuleSoft Anypoint API Manager?

Mulesoft Anypoint API Manager is the portion of the Anypoint Platform that is used for the designing, building, managing, and publishing of APIs. Anypoint Platform uses Mule as its core runtime engine.

Mulesoft Anypoint API Manager is an extremely versatile solution. It offers users the ability to deploy their APIs in a number of different settings. You can use API Manager on a public cloud, a private cloud, or a hybrid. Additionally, users can use the solution to manage their deployments with ease. A few clicks are all you need to alter your deployment.

Benefits of Mulesoft Anypoint API Manager

Some of the benefits of using Mulesoft Anypoint API Manager include:

  • The ability to deploy APIs and integrations in the location of your choice. Mulesoft Anypoint API Manager enables users to deploy APIs on their own servers or on the cloud via Mulesoft’s cloud service. It also allows users to change the deployment location with only a few clicks.
  • The ability to automatically protect your APIs with cutting-edge security software and protocols. Mulesoft Anypoint API Manager’s security software can automatically detect attacks against your APIs. This triggers an escalation of security protocols that push the attack to the perimeter of the system. The solution then proceeds to seal up any vulnerabilities. Mulesoft uses machine learning in order to adapt to any new threat that emerges.

Reviews from Real Users

Mulesoft Anypoint API Manager is a highly effective piece of software whose purpose is to enable users to design, build, manage, and publish APIs. It stands out among its competitors for a number of reasons. Two major ones are the ease with which users can connect it to their applications and the high level of value that its support offers. It provides users with the ability to easily connect this solution with whatever program they need to join it with. Users can create connections without having to write code. It offers different types of support which ensure that users have a high level of understanding about the product and how to use it.

PeerSpot user Tolulope A., a technical lead specializing in integration and middleware at a financial services firm, notes the ease with which users can connect Mulesoft Anypoint API Manager to their applications. He writes, “One good thing about MuleSoft is that they have a lot of connectors to those back-end applications. We don't really need to write code to be able to connect to a database or to connect with SAP. You just need credentials and the connectivity details. Most of the development of what we do is just drag and drop. They're able to connect with applications using standard connectors that are provided by ESB, by MuleSoft.”

The CEO & Co-Founder at a computer retailer notes the value of Mulesoft’s supporting documentation. They write, “The documentation is great; it is always up-to-date and well-presented. If any details are missing, then there is a blog available that contains a lot of details. There are also channels on YouTube to help you better understand the solution and what some of the processes look like.”

MuleSoft Anypoint API Manager was previously known as Anypoint API Manager.

MuleSoft Anypoint API Manager Customers

Coca-Cola, Splunk, Citrix, UCSF, Vertu, State of Colorado, National Post, TiVo, Deakin, LLS, Oldcastle Precast, ParcelPoint, Justice Systems, Ube, Sumitomo Corporation, PacificComp, University of Witwatersrand, Groupe Initiatives, Camelot, Panviva

MuleSoft Anypoint API Manager Video

MuleSoft Anypoint API Manager Pricing Advice

What users are saying about MuleSoft Anypoint API Manager pricing:
  • "Pricing can be improved."
  • "I think that it is pretty expensive."
  • "The pricing for this solution is cheaper than GCP and Bluemix."
  • "Licensing fees are paid on a yearly basis."
  • MuleSoft Anypoint API Manager Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Global Head of Digital Cloud & Platform Services at a financial services firm with 10,001+ employees
    Real User
    Top 20
    A mature solution with good policy management but can be quite expensive
    Pros and Cons
    • "Technical support has been helpful."
    • "The initial setup, if you go back three or three and a half years, definitely, for us, was complex."

    What is our primary use case?

    We primarily use the solution for our APIs. We are moving from monoliths to API architecture and we have approximately 10,000 to 12,000 APIs across banks, which are hosted on this product. It also provides us a gateway service to ingress the traffic as well as whole policy management where stuff is taken care of from the PC Any Point. It also has some API-level runtime policy management, which we use.

    What is most valuable?

    The gateway service to ingress the traffic is great. 

    The whole policy management has been great. 

    It has some API-level runtime policy management, which is useful for us.

    The solution is extremely mature.

    You can scale the solution.

    What needs improvement?

    The only drawback is that, due to the fact that we are going into a completely API structured way of working, it is very tightly coupled with the vendor solutions. For example, the run times. What happens is when you have to do a change or you have to do anything, you have to rip off all the APIs and rebuild it.

    If you see the features, they are really good in one sense, however, they have a certain drawback when you get into the operational way of working. We definitely need APIs to have policies at runtime. They provide a feature where there's a lot of policy on authorizations, however, the only problem is the runtime. 

    When the runtime upgrades, we have to basically publish a new build pack and then do all the rebundling. When we were 2000, 3000 APIs, it was okay. However, when you start going up to 10,000 to 12,000 APIs, it was too much.

    The whole cost is an issue. Deploying to production is not a very easy job in that bank as we go through the whole change process. The whole tight coupling of the product is a problem. 

    As a bank, we didn't want to take any risk of getting so much tightly coupled with any vendor product. It should be replaceable as required. That's the only reason we are now changing products.

    The upgrade is a very messy process. Mule 3.X to 4 or 4.2 requires you have to rewrite the APIs. It is not just upgrading the build pack with a runtime. That is something that gets us scared a lot. They came back and told us when we move to four run times we had to upgrade. You had to rewrite the APIs. The APIs cannot just work in a straightforward manner. There is a lot of change and we have approximately 5% Mule APIs and then the rest are boot APIs. While, now, that means 5,000 APIs need rewiring, after two years, we might have 20,000 APIs. They should have a proper way of having backward compatibility.

    The initial setup is complex. 

    If they are going with that control pane in a cloud, which is a very good feature and it is a managed service, they should give it 24/7, 100% uptime. They should also spin it across multiple regions. Currently, they are just the US and the EU is coming up. However, they should add, for example, China or Asia, et cetera. We operate in more than nearly 40 countries. Every country has a lot of its own governance and compliance and regulatory checks or some, where we cannot host to the cloud.

    For how long have I used the solution?

    We have used the solution for three and a half to four years at this point.

    Buyer's Guide
    MuleSoft Anypoint API Manager
    September 2022
    Learn what your peers think about MuleSoft Anypoint API Manager. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
    633,952 professionals have used our research since 2012.

    What do I think about the stability of the solution?

    We have a massive set up and definitely, there are sometimes a few issues, which come here and there, however, we manage to build a resiliency inside that.

    What do I think about the scalability of the solution?

    We have scaled from a few hundred APIs to 10,000 APIs. Just on the retail part, the gateway service runs more than 125 million transactions per day. It's a huge setup we have. 

    The only drawback back again is that their gateways are pretty heavy on hardware. Therefore, we spend a lot of money on the hardware. If you compare with Kong, Kong actually can just replace everything with two VMs. We have 500 VMs running for us as gateways. It has scalability, however, it will cost you, which is a problem.

    How are customer service and support?

    Technical support has been helpful. There were also people embedded in my team.

    Which solution did I use previously and why did I switch?

    We are migrating from Mule to Kong now. We just have signed the contracts and we are basically getting the thing set up. It is a big project and it is going to take maybe another three to four months to roll it out to non-production and maybe another five months into production as we need to get everything in compliance and clear.

    How was the initial setup?

    The initial setup, if you go back three or three and a half years, definitely, for us, was complex. As a bank, we run through a lot of securities. Since then, they have matured the process. They worked with us, to do some upgrades. Kong also will have to do a few things for us, once we migrate. Currently, we are already finding some issues, which Kong is trying to help us and fix it. However, Mule took a bit of time to set up. If we were to do it now, it would be easy. 

    They have come up with API management and cloud hub, which is the manual service. We have not used it much, however, there are some use cases from a different part of the bank that tried it out. It's a good option as you get rid of the whole operational management side of the whole control pane. The control pane we are running is a PC 1.7.3 or something, which is old and coming up on the end of support.

    The cloud hub may solve the problem of the control pane, even though they have some issues with the maintenance windows and stuff. Due to the fact that the policies are cast in the control pane, and run times can struggle, if the control pane goes down or needs maintenance because we need a hundred percent of availability in some way or other, it needs to be resilient also. The maintenance windows can cause trouble for us in banking.

    What's my experience with pricing, setup cost, and licensing?

    We originally signed a three-year licensing agreement.

    There's room for improvement on the licensing. They could do better.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    SVP - API integration, Fintech, Solution Architect, Delivery and Digital Lending at a financial services firm with 10,001+ employees
    Real User
    Top 20
    Good runtime fabric and API management, but doesn't scale well
    Pros and Cons
    • "The stability overall has been pretty great."
    • "We find that the enterprise level is lacking scalability."

    What is our primary use case?

    We primarily use the solution for API management.

    What is most valuable?

    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.

    What needs improvement?

    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. 

    For how long have I used the solution?

    I've been using the solution for four years.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    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.

    How are customer service and support?

    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.

    How was the initial setup?

    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. 

    What about the implementation team?

    We did have assistance from MuleSoft support.

    What's my experience with pricing, setup cost, and licensing?

    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. 

    Which other solutions did I evaluate?

    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. 

    What other advice do I have?

    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. 

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Buyer's Guide
    MuleSoft Anypoint API Manager
    September 2022
    Learn what your peers think about MuleSoft Anypoint API Manager. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
    633,952 professionals have used our research since 2012.
    Senior Manager at Accenture
    Real User
    Good API management capabilities, Composable Architecture and Auto-Scaling
    Pros and Cons
    • "It provides all of the robust platform-enabled features."
    • "When compared to other integration technologies, it is slightly higher."

    What is our primary use case?

    API Led Composable Architecture and Batch Integrations to deal with big volumes

    How has it helped my organization?

    API Manager helped to make api's discoverable, there by improved reusability.

    What is most valuable?

    IPAAS Cloudhub Platform, API Manager, Flex Gateway, RTF deployment Support, Connectors.  All these enabled to build, re-use and deploy the integrations faster.   

    What needs improvement?

     Mulesoft is on the higher end in terms of pricing. Clients frequently compare the price of various integration technologies for their use-cases. This is considered high for small/mid - scale enterprises with some tens of APIs to be build and managed.  Different pricing model that best suits for small/mid enterprises could help for more adoption.  As Mulesoft is a part Salesforce ecosystem, special discounts could be provided for Salesforce users for doing their integrations.  <10% of Salesforce projects are using Mulesoft and there is a huge potential. 

    For how long have I used the solution?

    I have been working with various versions of MuleSoft for more than 10 years.

    We are currently working with the latest version.

    What do I think about the stability of the solution?

    Mulesoft Anypoint API Manager is pretty stable.

    We use the CloudHub which is the MuleSoft cloud version it has everything that is required for a product with high availability and reliability. It's pretty stable.

    What do I think about the scalability of the solution?

    From a product standpoint, MuleSoft offers auto-scaling options that can be enabled. However, the majority of organizations will control it manually to avoid unpredictable higher costs.  overall,  application can be scaled easily.

    How are customer service and support?

     Depending on the subscription and severity of the case, technical support prioritizes the support cases. 

    I would rate the technical support a three out of five.

    How would you rate customer service and support?

    Neutral

    Which solution did I use previously and why did I switch?


    How was the initial setup?

    CloudHub is straightforward. There are alternatives as well like RTF that can be deployed on any cloud or bare metal,  On-premises deployments . It's more complicated if it's on bare metal. Mulesoft have professional services team that can assist on initial setup. 

    I would rate the CloudHub setup a four and a half out of five, and for an on-premises setup, I would rate it a three out of five.

    What's my experience with pricing, setup cost, and licensing?

    Pricing cannot be shared because it varies depending on the client's engagement with MuleSoft and subscription.

    Which other solutions did I evaluate?

    dell boomi, informatica, software AG

    What other advice do I have?

    Mulesoft provides platform to build and deploy huge number of APIs  with good API Management capabilities.  It also supports reuse of api's that are build on other platforms. With recent introduction of RPA,  we foresee a lot of scope to automate some human tasks. With MuleSoft Composer, non technical users can build small integrations quickly. 

    I would rate MuleSoft Anypoint API Manager an eight out of ten.

    Mulesoft supports API-led architecture excellently.  But not every integration use-case fits in this architecture.  Integrations that need to deal with large volumes needs a batch pattern that can be well performed with other integration tools.  EDI integrations that are widely used across large-scale enterprises. There is Anypoint Partner Manager specifically designed for EDI support, but it is little complex when compared with other EDI solutions that are in the market. A special component to deal with ETL integrations could improve the adoption.   EDI integrations could be simplified further.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Tolulope Adeniji - PeerSpot reviewer
    Technical Lead - Integration/Middleware at a financial services firm with 10,001+ employees
    Real User
    Top 5
    Good stability with responsive technical support and lots of connectors for backend applications
    Pros and Cons
    • "The solution has been very stable."
    • "Their analytics needs a lot of improvement. It's really lacking right now."

    What is our primary use case?

    We use it for integration with backend applications. We use it to connect to applications like SAP databases, or Infomatica Collibra or MongoDB, and some other backend applications.

    What is most valuable?

    One good thing about MuleSoft, is that they have a lot of connectors to those backend applications. We don't really need to write code to be able to connect to a database or to connect with SAP. You just need credentials and the connectivity details. Most of the development of what we do is just drag and drop. They're able to connect with applications using standard connectors that are provided by ESB, by MuleSoft.

    The initial setup is very straightforward.

    The solution has been very stable.

    Technical support has been great.

    What needs improvement?

    If you want to see the full-fledged functionality of their analytics engine, you have to pay separately for that. It's not the case with, for example, Apigee. That is out of the box. For MuleSoft, then you need to specifically pay an additional licensing fee be able to get the benefits of the analytics.

    It would be ideal if they had full-fledged features out of the box versus having to pay for them separately. 

    For how long have I used the solution?

    I have five years of experience using this product.

    What do I think about the stability of the solution?

    The product offers a very stable platform. We've had a couple of issues, however, it's a stable platform overall. Due to the API, there may be some buggy codes. We have not had any major issues, and, if we do, the technical support is very responsive to our queries.  

    How are customer service and technical support?

    Technical support has been excellent. Whenever we've had to contend with a bug, they have been very helpful at assisting us. We're very satisfied with their level of service. They are extremely responsive and very knowledgeable.

    How was the initial setup?

    The initial setup is very straightforward. It's much more straightforward, that, for example, Apigee, which is more difficult to execute.

    What was our ROI?

    The product added a lot of value to the organization. Usually, all integrations are point to point. For example, if Informatica needs the information from SAP or SAP from PeopleSoft,  they have point to point connection. Due to the fact that we are able to handle connectivity using MuleSoft, it's actually reusable for applications. Therefore, once we connect to SAP, we don't need to deal with that connectivity again. Any other application that needs to connect to SAP reuses the same API that we have developed on this platform. They don't really need to develop a new set of API.

    What's my experience with pricing, setup cost, and licensing?

    The solution makes users pay integration fees.

    You need to pay extra to get proper analytics. It's a separate fee.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Lead Consultant at HCL Technologies
    Real User
    Is easy to deploy and configure, and is highly stable and usable
    Pros and Cons
    • "MuleSoft has given the API solution a 3-tiered architecture. This means that there are multiple channels available in one application. The usability is very high."
    • "MuleSoft has advanced features but is slower."

    What is most valuable?

    You can find SLA there. You can do the security level that you need. You can also do any authentication, authorization, implementation, etc.

    You can create it yourself and publish it. While publishing, if there is a unique ID generated by that, it will be implemented there while creating the application. While deploying to the cloud, the Mule runtime is internally created and embedded in the API Manager.

    All of these features are available in the cloud, and you can configure it. It is of great benefit to the customer.

    MuleSoft has given the API solution a 3-tiered architecture. This means that there are multiple channels available in one application. The usability is very high.

    What needs improvement?

    MuleSoft has advanced features but is slower.

    For how long have I used the solution?

    I've been working with this solution since 2017.

    What do I think about the stability of the solution?

    It is highly stable, and that's why MuleSoft is booming. Mulesoft Anypoint API Manager internally uses the AWS availability zone. When one availability zone is down, then it will automatically route to another availability zone. You will not find this kind of stability on-premises because you can have server issues. However, on the cloud it's very stable and very reliable.

    What do I think about the scalability of the solution?

    MuleSoft has horizontal and vertical scaling capabilities.

    How are customer service and support?

    The technical support is good, but it is a new solution, so it will take time to mature. I would give technical support a nine out of ten.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    The initial setup is easy. You may have some issues when you deploy it for the first time if the team is new, but once you do it, the next time it will not take much time.

    You just need half a day or one day of training, and any team member can implement the solution.

    Maintenance wise, it doesn't require a lot because it's on the cloud. You do have to monitor some things on your end, but other maintenance issues are taken care of by MuleSoft.

    What other advice do I have?

    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.

    Disclosure: My company has a business relationship with this vendor other than being a customer: integrator
    Flag as inappropriate
    PeerSpot user
    AmitKanodia - PeerSpot reviewer
    Director at Capgemini
    Real User
    Top 20
    Responsive technical support, low tickets issued showing great stability, and limitless expansion
    Pros and Cons
    • "I believe the API connectivity within the cloud marketplace is most valuable."
    • "I think that they can bring some transparency in reference to the terms of the microservices architecture."

    What is our primary use case?

    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. 

    What is most valuable?

    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.

    What needs improvement?

    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. 

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

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

    How are customer service and support?

    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. 

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    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.

    What about the implementation team?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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. 

    What other advice do I have?

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

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    CSM -PCBU at Tata Consultancy Services
    Real User
    API management tool that is reliable with a wide range of connectors that are readily available
    Pros and Cons
    • "When using the Mulesoft Anypoint Platform, it has a wide range of connectors that are readily available to connect with the multiple applications."
    • "Migrating any existing middleware platform to Mulesoft is difficult because of the transformation, conversion and integration involved. Better tools are needed to achieve quicker time to market."

    What is our primary use case?

    I have used this solution for an Europe based customer. They have ticketing tools like ServiceNow and other applications in their multiple locations including Asia, the Pacific and North America. The idea was to integrate data communication between those applications.

    What is most valuable?

    When using the Mulesoft Anypoint Platform, it has a wide range of connectors that are readily available to connect with the multiple applications. They have specifically categorized the API application into three parts; backend APIs, middle APIs (which handles a business process), and front end layer APIs. These distributed API applications make Mulesoft a well matured and organized platform. 

    What needs improvement?

    Migrating any existing middleware platform to Mulesoft is difficult because of the transformation, conversion and integration involved. Better tools are needed to achieve quicker time to market.

    The security infrastructure for this solution could be improved. Other API tools have more security options available. API Connect, for example, has specifically designed policies where I can customize my security framework for internal and external users. That kind of infrastructure is not available with Mulesoft.

    For how long have I used the solution?

    I have used Mulesoft API Management for one year. 

    What do I think about the stability of the solution?

    This is a stable solution if the hardware is set up properly. You need to monitor the load of the APIs and the bandwidth they use to achieve maximum throughput. 

    What do I think about the scalability of the solution?

    This is a scalable solution. 

    How are customer service and support?

    We have hardly needed assistance from a technical perspective because their infrastructure is powerful and after sale service is good. I would rate it a four out of five.

    How was the initial setup?

    The initial setup is complex when it comes to establishing the connectivity between on-premise services and cloud services. Deployment took between six and eight months. We have two junior resources who are responsible for maintenance but the solution does not require much maintenance after being pushed to production. 

    What was our ROI?

    Mulesoft is great in terms of reusability. When I design APIs for backend application, they can be reused because they are independent of the business flow. It is a good overall solution compared to other API management technologies with a quick time to value. 

    What's my experience with pricing, setup cost, and licensing?

    The pricing for this solution is cheaper than GCP and Bluemix.

    What other advice do I have?

    I would rate this solution a seven out of ten. 

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    General Manager at HCL Technologies
    Real User
    Top 10
    Helpful technical support and responsive community, but the performance could be improved
    Pros and Cons
    • "Its best feature is that its plugins are somewhat unique in the market. We have budgets, Prime membership, and pre-plugins available in the marketplace that we can use immediately."
    • "Their studio performance is very slow, it requires a lot of memory, and should be improved."

    What is our primary use case?

    I am offering consulting services to help clients build the API. I am not involved in the deployment or anything behind the API.

    We are using the Anypoint component for the integration layer which is not specific to the API management.

    What is most valuable?

    Its best feature is that its plugins are somewhat unique in the market. We have budgets, prime membership, and pre-plugins available in the marketplace that we can use immediately.

    What needs improvement?

    I believe there is an issue with MuleSoft, specifically the studio, it is very slow.

    The performance could be faster. Their studio performance is very slow, and it requires a lot of memory which should be improved. 

    It is not as compatible as other options available.

    You would like to improve studio performance in the next release.

    For how long have I used the solution?

    I have been working with Mulesoft Anypoint API Manager for three years.

    What do I think about the stability of the solution?

    Mulesoft Anypoint API Manager is very stable.

    What do I think about the scalability of the solution?

    Mulesoft Anypoint API Manager is a scalable product.

    We have 300 users in our company, and we use approximately 10,000,000 hits per day.

    We will definitely increase our usage. It should be standard as a requirement model. It's not specific. We have a capability team, and the capability team gives us access to that information. We have a plan, but we cannot provide specific data numbers because of time constraints.

    How are customer service and support?

    The technical support is very good. One of the best things about MuleSoft is its community. They provide support if you raise an issue in the MuleSoft community they will respond. Anyone who is available will respond and resolve your query as soon as possible.

    How was the initial setup?

    I was not involved in the installation.

    What's my experience with pricing, setup cost, and licensing?

    Licensing fees are paid on a yearly basis.

    What other advice do I have?

    Definitely, I will recommend Mulesoft Anypoint API Manager over IBM App Connect.

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

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Download our free MuleSoft Anypoint API Manager Report and get advice and tips from experienced pros sharing their opinions.
    Updated: September 2022
    Product Categories
    API Management
    Buyer's Guide
    Download our free MuleSoft Anypoint API Manager Report and get advice and tips from experienced pros sharing their opinions.