Data & Analytics Architect at BM&FBOVESPA SA Bolsa de Valores Mercadorias e Futu
Real User
Top 5
2023-06-01T16:00:00Z
Jun 1, 2023
Areas of improvement include marketing and enhancing the data products area by using ETIs. Also, we need to improve communication and data exchange using ETS and EPS. Additionally, nowadays they're using another product in the cloud. However, they also have their own product.
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.
Associate Software Engineer at Tech Mahindra Limited
Real User
2023-01-23T19:08:31Z
Jan 23, 2023
Sometimes we find bugs where certain calls are not returning all the data we need. This means the data can become obsolete and non-visible. This needs to be fixed.
In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better. Sometimes, in our recent experience, we noticed that our engineers were much more advanced than the tech support. Our team found some challenges, problems, and issues. We sat down together and found the solution ourselves.
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.
Axway API Management Plus combines API lifecycle management, secure integration services, monitoring and analytics to help you innovate faster and heighten ecosystem engagement. It is part of the Axway AMPLIFY data integration and engagement platform, which also includes unified app development for mobile to provide a complete solution for rapid change and innovation.
Axway's queuing messages could be enhanced.
Areas of improvement include marketing and enhancing the data products area by using ETIs. Also, we need to improve communication and data exchange using ETS and EPS. Additionally, nowadays they're using another product in the cloud. However, they also have their own product.
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.
Sometimes we find bugs where certain calls are not returning all the data we need. This means the data can become obsolete and non-visible. This needs to be fixed.
In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better. Sometimes, in our recent experience, we noticed that our engineers were much more advanced than the tech support. Our team found some challenges, problems, and issues. We sat down together and found the solution ourselves.
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.