by ak217 on 8/11/16, 5:16 PM
I 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.
by impostervt on 8/11/16, 4:27 PM
API 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?
by pilom on 8/11/16, 4:46 PM
So 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.
by namero999 on 8/11/16, 4:50 PM
I 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?
by PaulHoule on 8/11/16, 5:09 PM
It 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.