What is Amazon API Gateway?
What is Apigility?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Amazon API Gateway?
What are the cons of using Apigility?
Apigility is loyal to the standards; we do not need a framework to write custom REST APIs, anyone can do that; we need a framework that makes sticking with the standards easy.
Every PHP framework should be designed in such a way, that it forces you to think about what you are doing, the current PHP mind-set is too much crowded with lazy documentation of custom-solutions that do not work as expected (because the language gives you too much freedom).
With Apigility it is easy to build RESTful APIs in a declarative way, so that you do not need to write tests for every API Service you create, because the underlying code doesn't change or break, all functionality comes within the framework, that has already been tested.
You do not need to write any boiler plate code, which is huge plus compared to Symfony 2 and the likes.
Apigility has had some reliability problems with newest releases and as far as I know, they do not report which release is the latest stable. But of course, they reached the 1.0 in 2015.
If you're building an API service, this Chrome extension is a must-have. It'll let you ping your endpoints using a nice clean UI that's built right into Chrome. You can also share your previous requests - a simple way to 'document' your API if you're short on time.
If someone is having trouble shipping data to the Knowtify API, I almost always share my postman collection. Working through the issue from there is typically pretty easy.
Not much to say, it's the best free tool out there for testing APIs. Get it.
API Gateway in conjunction with Lambda has allowed us to become 'serverless'. We have a number of API endpoints that range from simple CRUD operations, through to triggering chains of complex background jobs. Like Lambda, this service has released us from getting bogged down in infrastructure management, freeing up huge amounts of time to focus on solving business problems.
Postman is a powerful tool for performing integration testing with your API. It allows for repeatable, reliable tests that can be automated and used in a variety of environments and includes useful tools for persisting data and simulating how a user might actually be interacting with the system
We use Postman in conjunction with our universal REST-API "JCVortex". Postman makes testing edge-cases hassle-free and lets testing look easy. Postman was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.
I use it for testing my Web Api. It's a easy tool for interacting with a RESTFul API and provides great tools for organizing requests. The Newman tool is great for allowing your tests to run in a CI/CD pipeline.
Used to test API endpoints and monitor API which also acts as an API heartbeat to keep functions alive in Google Cloud in order to avoid timeout responses to Slack.
We use Postman for all our API testing. Postman is invaluable. We would like to have a team licence so that we can use shared work spaces and test collections.
It provides me with POST endpoints; I don't run servers and some third-party services need to POST data to my application.
Triggers the Lambda function from a GitHub WebHook push into
Excellent API Gateway, some quirks but most are being addressed over time, easy integration with Lambda