Chief Integration Architect at a logistics company with 10,001+ employees
Real User
2021-02-17T18:00:03Z
Feb 17, 2021
The API Mocking tools need to be improved. To start with an API-first approach would benefit this product. We sometimes have issues with some of the functions because they do not work very well. Specifically, there are some policy-related functions that should be enhanced for better usability and maintenance. The developer portal is restricted and it should be enhanced to handle direct API managers. This would be a plus because right now, the strategy is more focused on AMPLIFY, which is hosted in the cloud. However, we are not always interested in publishing our API on the cloud from the vendor. Rather, we want to have it in our own cloud. The only product that we can install on-premises is the API Portal, and it is restricted.
The portal still has room for improvement. This is in terms of speeding up the overall process of creating new documentation and new information about the APIs. They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome. Technical support, although it's very good, there is room for improvement.
The pricing could be more competitive. The installation process is a bit complex and it could be a lot simpler. Currently, there's a strong focus on microservices, which is already there and already available. They're already able to deploy in dockerized containers. In that sense, there's nothing that I can actually see that is missing from my side.
Digital Enterprise Architect at a energy/utilities company with 10,001+ employees
Real User
2019-09-27T04:38:00Z
Sep 27, 2019
This solution does have some limitations regarding the deployment model. This has nothing to do with the features. Rather, we are deployed in a single region, and not everywhere. Our biggest concern is to have a solution that can be used all over the world, in all regions. The scalability of this solution could be improved.
I think that the program's team management capabilities can be better as far as working in groups. I really am interested in several of the new features already announced and being offered in the release of version 7.6.2. That is the main reason why we want to upgrade. Beyond those features, I don't know that anything needs to be added right now.
Integration Architect / Specialist at a tech services company with 11-50 employees
Real User
2019-07-18T11:31:00Z
Jul 18, 2019
The product community is not good. We don't get a lot of support from them in resolving issues. A feature that would be good to have is support for microservices and containerization. The setup is actually pretty complex and could be improved so maybe in the next update they could do something to simplify setup, make Axway more stable, and get rid of existing technical issues.
Digital Enterprise Architect at a energy/utilities company with 10,001+ employees
Sep 27, 2019
The platform is more expensive than a full cloud solution like AWS API GW. Setup cost depends on deployment target : on premise / shared cloud tenant / dedicated cloud tenant.
Digital Enterprise Architect at a energy/utilities company with 10,001+ employees
Sep 27, 2019
The platform is more expensive than a full cloud solution like AWS API GW. Setup cost depends on deployment target : on premise / shared cloud tenant / dedicated cloud tenant.
The API Mocking tools need to be improved. To start with an API-first approach would benefit this product. We sometimes have issues with some of the functions because they do not work very well. Specifically, there are some policy-related functions that should be enhanced for better usability and maintenance. The developer portal is restricted and it should be enhanced to handle direct API managers. This would be a plus because right now, the strategy is more focused on AMPLIFY, which is hosted in the cloud. However, we are not always interested in publishing our API on the cloud from the vendor. Rather, we want to have it in our own cloud. The only product that we can install on-premises is the API Portal, and it is restricted.
The portal still has room for improvement. This is in terms of speeding up the overall process of creating new documentation and new information about the APIs. They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome. Technical support, although it's very good, there is room for improvement.
The pricing could be more competitive. The installation process is a bit complex and it could be a lot simpler. Currently, there's a strong focus on microservices, which is already there and already available. They're already able to deploy in dockerized containers. In that sense, there's nothing that I can actually see that is missing from my side.
It would be great if they have an asset report. It's hard to get support for that.
This solution does have some limitations regarding the deployment model. This has nothing to do with the features. Rather, we are deployed in a single region, and not everywhere. Our biggest concern is to have a solution that can be used all over the world, in all regions. The scalability of this solution could be improved.
I think that the program's team management capabilities can be better as far as working in groups. I really am interested in several of the new features already announced and being offered in the release of version 7.6.2. That is the main reason why we want to upgrade. Beyond those features, I don't know that anything needs to be added right now.
The product community is not good. We don't get a lot of support from them in resolving issues. A feature that would be good to have is support for microservices and containerization. The setup is actually pretty complex and could be improved so maybe in the next update they could do something to simplify setup, make Axway more stable, and get rid of existing technical issues.