What is our primary use case?
We use Axway Amplify API Management for primarily two use cases. The first one involves an API Gateway exposed on the DNC layer to allow external organizations to connect to internal APIs. The second use case is when applications within the organization need to connect to already hosted APIs, which is done through an internal gateway. These two use cases are supported by APIs built around them.
What is most valuable?
The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times.
What needs improvement?
The areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options.
If there was a new release of this solution there should be a feature called "Revision History" or "Version Control" that would allow developers to easily navigate and compare different versions of their API flows within the Amplify API Management toolkit. This would save time and effort by eliminating the need to constantly switch between the toolkit and external Git repositories. Additionally, it would provide an added layer of security by allowing developers to quickly revert back to previous versions if a mistake or issue arises.
For how long have I used the solution?
I have been using Axway AMPLIFY API Management for approximately four years.
What do I think about the stability of the solution?
The solution is stable. It is evident by its impressive features, such as zero downtime and various other elements that ensure the constant availability of your APIs. However, if the volume of usage was to increase, then certain specific measures would need to be taken in order to maintain the aforementioned stability.
What do I think about the scalability of the solution?
There is an issue with the scalability of the solution. This can be attributed to the internal database, Cassandra, that it employs. In order to accommodate a large volume of requests coming into the gateway, the traditional practice was to install both Cassandra and the gateway on the same on-premise server. However, with an increase in the number of request volumes, scaling up has become problematic. As a result, it has become necessary to install multiple instances of a Cassandra server and gateway separately.
We have approximately 200 to 250 people using the solution who are deployed to different projects.
How are customer service and support?
We have used the technical support team of Axway AMPLIFY API Management. Even though their responses are always very timely, we found ourselves in frequent interaction with them. This can be attributed to the high volumes and complex setup that we have, resulting in a minimum of two to three tickets being raised each month.
The majority of the time we used the support we had answers, but in some cases, we were able to figure out the solution without help after we created the tickets.
I rate Axway AMPLIFY API Management an eight out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have used various other API Management solutions, such as Apigee. Apigee is now on the cloud.
How was the initial setup?
The initial setup of Axway AMPLIFY API Management is easy.
The amount of time it took to set up and launch everything, including spinning up instances and completing environment setup for development or quality involvement, the entire process took approximately one week to finish. Additionally, it's worth noting that the spinning up of a new API gateway instance was a relatively quick process. It's possible that the deployment could be accomplished faster if you're solely focused on this aspect of the process. Furthermore, as part of the deployment process, both penetration and load tests were conducted to ensure everything was functioning properly.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive. When you acquire a license you have full access to the solution, unlike other competitors such as Apigee X, where there are fragmented licenses. Some licenses only allow access to certain features while others allow access to more features. Upon procuring this solution's license, you will have full access to the solution, allowing you to experiment with all of its features.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises