Amazon API Gateway vs. Postman

API GW is great for giving access to asynchronous operations that are fast and don't need to be online all the time. Lambda functions are the classic example. In the past, an operation that is called on via an HTTP endpoint would be implemented using a server-based solution. With high availability in place that would include a server or two and a load balancer. Over time this setup can be costly, especially if the service is not used at full capacity; cycles are wasted when the servers are sitting there waiting to respond. If the operation can be distilled down to a function, an API GW + Lambda solution could be put in place that performs the operation as needed only when requested. Comparing the low price point for API GW requests and Lambda CPU+Memory, the savings can be night and day over the server-based implementation.

Incentivized

Postman is good for organising your API credentials, vendor settings, environments etc. It's also a good way of getting stared with APIs as you get to use a GUI which can help you understand what we mean by a 'body' or 'bearer token'. I think people generally gravitate towards GUI tools for getting started in a new technology area.

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

• It has opened a door for me to explore more out of it, as it is associated with so many APIs that I never felt any difficulty in finding the right API template, which are well organized and easily available.
• It is very secure to use and provides great services which are user-friendly.
• Due to this software I have got rid of the excessive emails and the slack channels, Now I am using my own private API and even it give me an option to produce my personal Postman’s API Builder from its Private API Network and this features has shared my excessive workload.

Incentivized

• I think there should be another way of enabling CORS. It basically creates OPTIONS for every endpoint, which makes your API Gateway look complicated.
• The integration timeout limit is 30 seconds, which limits you into that time.
• API Gateway UI should be improved and should work correctly when more than two people are adding/editing endpoints.

Incentivized

• Wherever you need to automate tests that involve database verification or rely on data from databases, Postman is less suitable.
• Postman's disc usage is extremely high, and it occasionally causes the computer to fade.
• It doesn't have the ability to generate random data. To achieve randomness in my tests, I've been working around scripts.

It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system

Incentivized

1. Friendly user friendly - when I started using Postman, I was a beginner to the API world, and it gave me a friendly view to begin its usage 2. Postman offers many features, including API testing, monitoring, documentation, and mock servers 3. Environment variables simplify testing across multiple environments (dev, prod) without repetitive configuration.

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

There is a lot of in-depth documentation for Postman available online, including detailed guides with screenshots and videos. They provide example APIs for new users to explore while learning how to use the tool. Generally, bugs in the client are quickly addressed through frequent free updates. Community and professional support options are available - most of the time, the free/community level support is adequate

Incentivized

Pricing is better at Amazon API gateway. Amazon API gateway is more user-friendly than SAP HANA Cloud. But SAP HANA Cloud supports more programming languages. The centralized management and monitoring system of Amazon API Gateway is more user-friendly. The User-Interface of Amazon API gateway is also better. Overall we can conclude that Amazon API Gateway provides a better work experience than SAP HANA.

Incentivized

Previous to using Postman, I would either use browser tools directly, or write an in-house tool to send requests. Postman eliminates that need while providing a much better experience and more features. At the base level, Postman is as simple as typing in the address as you would in a browser. Authentication can be provided simply as well.

Incentivized

• Positive, which accelerated business deliveries in months
• Negative, but in our positive case, if you are going to change the solution in the future, you need to adjust several things for the new solution.
• Positive, users celebrated with ease of use (lower learning curve, lower cost).
• Positive - Pay according to usage

Incentivized

• Postman is free (although there's a paid tier that offers more features) so using it for testing APIs comes with little to no risk (besides learning curve).
• The learning curve is a little steep for non-developer users, but developers should find it easy to pick up and use right out of the box, so to speak.

Incentivized