Amazon API Gateway

20 engineers on Hacker News describe using Amazon API Gateway first-hand: 5 endorse it, 2 regret it, 2 are mixed.

64%trust
20first-hand users
18in production
endorse 5mixed 2regret 2uses, no opinion

“both Cognito and especially API Gateway are somewhat convoluted to configure. They seem to work fine once you have them setup right”

mixed · production · nijave · 2026-05-10 · source ↗ · wrong label?

“I do currently enjoy not having to manage anything myself and I like that there's no internal abstractions”

endorse · production · politelemon · 2022-08-01 · source ↗ · wrong label?

“The API Gateway and ALB code was pretty much a one-and-done, with the bulk of the work consisting of setting up TLS termination”

endorse · production · 2 yr · fivea · 2021-11-20 · source ↗ · wrong label?

“Managed services like Lambda and API Gateway were prohibitively expensive.”

regret · personal · cj · 2019-09-23 · source ↗ · wrong label?

“We switched to AWS serverless about a year ago (API gateway and Lambda) and there have been no real surprises.”

endorse · production · 1 yr · matchagaucho · 2019-09-23 · source ↗ · wrong label?

“we use API Gateway even for our VM hosted APIs for the other features it provides”

endorse · production · scarface74 · 2018-12-19 · source ↗ · wrong label?

“We use Lambda + API GW to manage the glue between our different data/service providers.”

endorse · production · laurentl · 2017-12-21 · source ↗ · wrong label?

“Lambda + API Gateway requests typically incur a ~200ms invocation latency”

mixed · production · gamache · 2016-12-05 · source ↗ · wrong label?

“The alternative is to create a whole new API gateway, but that means that once I get my stuff tested, I essentially have to recreate my new environment in production”

regret · production · cargomaster · 2015-07-16 · source ↗ · wrong label?

“API gateway ends up being more expensive every month than lambda.”

neutral · production · willio58 · 2023-11-12 · source ↗ · wrong label?

“the lambda is behind an api gateway resource/method”

neutral · production · retrocryptid · 2021-12-31 · source ↗ · wrong label?

“We run mostly on AWS - essentially Lambda/API Gateway/SageMaker etc”

neutral · production · jedwhite · 2021-06-11 · source ↗ · wrong label?

“API Gateway is only used for the top level route.”

neutral · production · mozey · 2021-04-19 · source ↗ · wrong label?

“Our terraform has infrastructure code for: API Gateways”

neutral · production · lovehashbrowns · 2020-10-12 · source ↗ · wrong label?

“Api-gateway -> Lambda -> NATS -> docker backend on GPU”

neutral · production · KaiserPro · 2019-07-31 · source ↗ · wrong label?

“Sometimes the graphql-server sends direct api-calls via api-gateway.”

neutral · production · keremkazan · 2018-12-05 · source ↗ · wrong label?

“I have spent the last year and a half building a completely serverless production service on Lambda, API Gateway, and DynamoDB”

neutral · production · 1.5 yr · not_kurt_godel · 2018-06-23 · source ↗ · wrong label?

“I do do a lot of the request parsing in the Lambda function itself, rather than letting API Gateway do this.”

neutral · personal · Vinnl · 2017-12-21 · source ↗ · wrong label?

“The GraphQL API is backed by DynamoDB and is served via API Gateway.”

neutral · production · leetbulb · 2017-12-05 · source ↗ · wrong label?

“we deploy a second function and switch the API Gateway over when we are good to go.”

neutral · production · Prefinem · 2017-06-21 · source ↗ · wrong label?