Service and Support
Users report mixed interactions with Axway AMPLIFY API Management support. Some indicate satisfactory resolutions and quick response times, noting helpful communication and ticket management. Others feel that while support can be timely, frequent interactions occur due to complex setups. Some mention the technical team’s ability to solve issues, but point out room for improvement in support quality, rating it average to good, with some suggesting enhancement is possible for greater operational productivity.
Deployment
Axway AMPLIFY API Management's initial setup experiences vary. Some users find it complex, especially with local customizations or security needs, while others highlight the ease in comparison to competitors like Apigee. Deployments often require support or specialized knowledge, but the process can be rapid, especially when leveraging modern technologies like Docker. Maintenance is feasible with a small team, and documentation aids those with experience. Deployments range from hours to weeks, depending on the setup's complexity and purpose.
Scalability
Axway AMPLIFY API Management is considered scalable by many, benefiting enterprises and startups. Some note challenges with internal databases affecting scalability, especially in on-premises setups, and manual scalability requirements. Cloud deployment offers potential, though infrastructure setup impacts scalability. Users report ease in quickly adding environments and managing high volumes, while benefiting from good price scalability. Despite these advantages, others highlight limitations compared to other solutions like AWS API Gateway.
Stability
Axway AMPLIFY API Management generally receives mixed feedback on stability. Some organizations report no issues and praise its reliability, citing its zero downtime and robust security features, particularly in financial services. Others note occasional technical challenges, especially during setup. Concerns exist regarding support in different time zones. Some suggest that its stability is contingent on usage levels, implying further testing in high-load scenarios could be beneficial.
