Usage Plans for AWS API Gateway
aws.amazon.com
Usage Plans for AWS API Gateway
1–10 of 25 posts
Re: Usage Plans for AWS API Gateway
#2API Gateway was a pain to use when it first came out. The API wasn't supported by AWS CLI and there were no good wrappers for it in Node.js (my preferred language for APIs).
Has the situation improved?
Re: Usage Plans for AWS API Gateway
#3API Gateway was a pain to use when it first came out. The API wasn't supported by AWS CLI and there were no good wrappers for it in Node.js (my preferred language for APIs). Has the situation improved?
API Gateway is supported from the cli: http://docs.aws.amazon.com/cli/latest/reference/apigateway/
and is part of the SDK for Node: https://aws.amazon.com/sdk-for-node-js/
Re: Usage Plans for AWS API Gateway
#4So this is why our API had a rash of 500 errors last night. We haven't been very happy with the uptime of this service, mostly because they do deploys that break things for a couple minutes about once a month.
Re: Usage Plans for AWS API Gateway
#5I like the service and I use it for mock endpoints and other non-production applications, but I never managed to make gzip compression work in API Gateway. Actually, it seems to me that even when the origin serves gzipped content, it comes out uncompressed from API Gateway. Clearly a no-go for mobile apps. Anyone had the same experience, or did I miss something obiouvs?
Re: Usage Plans for AWS API Gateway
#6So this is why our API had a rash of 500 errors last night. We haven't been very happy with the uptime of this service, mostly because they do deploys that break things for a couple minutes about once a month.
Do you use Lambda as a backend? If so, this might have been related to Lambda, not the API Gateway. I also saw a number of 500s, but upon further digging, the API Gateway was fine, but the Lambda functions it was invoking were returning "Service Error." Still not happy either way, but I've generally been impressed with the gateway product itself.
Re: Usage Plans for AWS API Gateway
#7It amazes me it took them long to get here.
Six months I was looking around and found that API gateways from various vendors addressed everything somebody might want in an API gateway except the one thing you need for a minimal viable product -- a way to charge for API calls.
Re: Usage Plans for AWS API Gateway
#8I wish they'd focus on speed and rebuilding API Gateway to be easier to use, or provided a new proxy option to run Lambda under. This set of changes doesn't seem to improve on any of the practical issues in using Lambda with API Gateway.
Re: Usage Plans for AWS API Gateway
#9I like the service and I use it for mock endpoints and other non-production applications, but I never managed to make gzip compression work in API Gateway. Actually, it seems to me that even when the origin serves gzipped content, it comes out uncompressed from API Gateway. Clearly a no-go for mobile apps. Anyone had the same experience, or did I miss something obiouvs?
API Gateway can't serve binary content, making it useless for anything but JSON toys.
Re: Usage Plans for AWS API Gateway
#10I wish they'd focus on speed and rebuilding API Gateway to be easier to use, or provided a new proxy option to run Lambda under. This set of changes doesn't seem to improve on any of the practical issues in using Lambda with API Gateway.
Latency was a concern at launch but it has improved a lot, I see less than 20 ms these days. Depends on scale though, we have moderate sustained load 24/7