Amazon API Gateway vs. Informatica Data Archive

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

Incentivized

To manage users, go to the admin dashboard, here is a section for users. In this users section here you can see which users are configured and you have the ability to suspend a user. If you want to edit or add users, you need to go to the Organization section, then click on another user section there, which then gives you the ability to edit or add users.

Incentivized

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

Incentivized

• Works well with curated data
• Allows you to monitor data movements within an organisation
• Advisable to use ILM if already using Informatica PowerCenter

Incentivized

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

Incentivized

• As we are still piloting the product at our company at this time the feedback is highly limited.

Incentivized

We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.

Incentivized

When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.

Incentivized

[The] customer support is quite good. Cost also has another point to add, along with process integration and ease of using new tool.

Incentivized

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

Incentivized

• it is also fully integrated with all other AWS services
• manages the entire life cycle of the Certificates by itself, so it will reduce your work by a really big amount
• it can also be easily integrated with ELB and front-end cloud services.

Incentivized