What advice do you have for others considering Axway AMPLIFY API Management?

The main benefits end users receive from Axway AMPLIFY API Management are numerous. Axway is an organization that creates different tools in the market. They have API, B2BI, and multi-file transfer known as MFT or FT. In the API area, Axway has been beautifully immersed from around 2014 to 2016 onwards and has captured the market in a beautiful way. The crux is that they are a product-based organization, which means they have their own licenses and costs for bearing those licenses, plus costs for conducting training online, which is not open source. I must pay the organization to get that training. These are the perks and cons of the organization. Competitors such as AWS API Gateway, Kong API Gateway, or Azure API-M are pretty good competitors of Axway. AWS and Azure are huge platforms that provide multiple different features to users, so API Gateway is just one of their one hundred applications. They are focused on many things. If I am at AWS, I can use Lambda along with AWS API Gateway, and there is a database and everything included. Although Axway AMPLIFY API Management has a very good niche market, the demand of users and employees using this tool is quite niche and not very easily available. When the organization needs to be performed right away at ground zero, the demand comes up. However, this does not mean that open source tools, such as AWS API Gateway, which has good training on the YouTube platform and different platforms, does not give competition to Axway. Axway AMPLIFY API Management has a specific feature in that since it is product-based, they have their own dedicated support team, their own escalation matrix, and subject matter experts. Whenever I am facing any issues at a platform level or product level, they provide a good timeline resolution. AWS and other organizations follow the same flow, but I am not sure how much time it will take. I have unlimited access as a member of Axway. It could be the same with Kong or with any other organizational tool. I am specifically talking about Axway. There are both pros and cons of using this feature of Axway. I aid my clients with Axway products. I would recommend Axway AMPLIFY API Management to other users because I have worked with this tool for quite some time and it is quite easily operational. It has a very good graphical user interface. It has an upper hand compared to AWS or Azure in that they are very blunt in specific formats of XML, but Axway AMPLIFY API Management gives graphical interfaces for visibility of how the API transactions are going from here to there. From the user visibility part, I would give this upper hand to Axway AMPLIFY API Management. My overall rating for Axway AMPLIFY API Management is eight out of ten.

I initially had a perpetual license with Axway, hosting the API gateway on-premises, but due to Axway's shift away from supporting Oracle Linux, we moved to a containerized model for hosting the gateway. Though these containers are not hosted on the cloud, they are hosted on the same virtual machines or infrastructure, allowing flexibility regardless of the operating system of the host machine. Overall, I would rate Axway AMPLIFY API Management at eight. The cloud hosting is costly for us, which led us to opt for a different model instead, and I feel that competitors such as Kong are emerging rapidly in the market, creating pressure on Axway to enhance their offerings, especially in the realm of API gateway hosting for microservices.

We are doing the solution’s maintenance with the help of six engineers. We use Axway in various use cases, including healthcare, financial services, and manufacturing. Its flexibility allows us to adapt to different scenarios. It is highly reliable, forming a backbone for our business. Axway has consistently delivered and has not let us down at all. Overall, I rate the solution a nine out of ten.

If you want to use Axway, it's recommended to expose your APIs, whether they are for internal or external consumers. I would rate it as a nine.

This is a good solution. However, for on-premise networks, this solution works well. I would recommend it to others. It is a highly stable platform with great filter and feature options. While there is still room for improvement in areas, such as toggling, traffic management, and gateway portal availability, overall it is a very impressive tool. I rate Axway AMPLIFY API Management a nine out of ten.

I give the solution an eight out of ten. The solution is highly emerging in the market. Plus, it is easy to understand and provides good jobs in this market. Therefore, I would say it is a niche tool that is one of a kind. In my current organization, there is a limited set of people who can use the solution because it is a licensed product. Not every customer has the requirement to use it. However, in my previous company, every other person was using the solution. Every customer who was engaged with us used Axway AMPLIFY API Manager because it was a product-based organization. The solution has received positive feedback from the organizations that are using it. However, not every day is perfect; sometimes there are glitches or connectivity issues. But even with these issues, some customers have been using the solution for more than five or six years. In fact, the number of users of the solution has increased by three times since I started working with it. From my experience, customers are loving Axway AMPLIFY API Manager. This is a product-based solution, so not all the information can be found on Google. Axway AMPLIFY API Manager is not open source. Some features are hidden behind the license pack that Axway sells to customers. I believe that if the organization is compatible enough or has enough money to purchase the solution, then it's a great solution. The documentation is great. And if the organization is capable enough to hire experts for the solution, then they won't have issues working with Axway AMPLIFY API Manager.

I'm not sure about this product yet, so it is 50/50 whether I would recommend it to someone or not. I would rate this solution as a seven out of ten. Other similar products have similar features, so this solution doesn't have anything that is more advanced.

We do not use point-to-point APIs. I would rate this solution a six out of ten.

I would recommend Axway AMPLIFY API Management for scalability and for how it's open for customizations. We can customize it to accomplish your specific needs, like the look and feel. But we still have some issues when we do a lot of customization and when migrating from one version to another. On a scale from one to ten, I would give Axway AMPLIFY API Management a nine.

We're largely a customer, although we are consultants and refer Axway often. While we use the solution's cloud deployment model, we also engage with the on-premises version as well. I'd advise other companies considering a solution like this to first go and determine their strategy around APIs in their business. That's really important. There needs to be a plan around how a company is going to manage APIs. A business needs to ask itself: What is the digital transformation strategy? They need to approach this as a strategic investment and already have some strategy behind it. It really is core to your digital transformation, to your ability to unlock new revenue channels for a lot of businesses or to reduce cost in your back office systems. Therefore, there must be some sort of strategic benefit that you see before you actually evaluate API platforms. Once you've got a strategy, you're sure that this matches your strategy. You probably need to also look at the first use cases that you want to do. You have to find a use case that shows a business benefit to deploying. It doesn't help you implement the solution just so that lots of people can use it for different things. You must find some anchor or use case that you will be able to sell. Then it will become a benefit to your internal business. From there on it's really, really important to identify integration partners that are certified that can actually assist you from a business point of view, to deploy quickly. The quicker you get the benefit, the quicker you get the new revenue from whatever you want it to do. After that, it's crucial to internalize the knowledge around the solution. It is important to do good skills transfer so that you can have confidence in using the solution long-term. Overall, I would rate the solution nine out of ten.

You should have an understanding of the capability of the API. MuleSoft has a very straightforward and good framework that allows the customer to follow through. They understand how we can create and maximize capability in many ways. With Axway, if you start to use and understand it, then you are able to enhance it. However, that needs time to develop. It also takes a lot of time to actually bring it up to the principal site. I would rate Axway a seven out of ten. Not a ten because of the pricing and technical support.

This is a good product, but we need to work outside of our single region. I would rate this solution a seven out of ten.

If I were a team going to deploy this solution now, I would probably deploy it using the newer containerized solutions for better flexibility. On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a ten. It does everything that we expect it to do and is developing features to match innovation in technology.

On a scale from one to ten, I would rate this product at around a five. Some of the features and capabilities are not as mature as other products on the market, some features are not as easy to use and may be better as the product matures. In my opinion, there are other solutions that are currently better than Axway. As far as giving advice to those considering the product, I suggest doing some pilot projects to check as to whether or not Axway suits your requirements before choosing to deploy.