If you were talking to someone whose organization is considering Axway AMPLIFY API Management, what would you say?
How would you rate it and why? Any other tips or advice?
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.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.