4 ms·

I love lambda's, but api gateway was far from mature the last time I used it (6 months ago). Unless they have made serious updates to the deployment workflow,

by gjolund 10y ago

I love lambda's, but api gateway was far from mature the last time I used it (6 months ago). Unless they have made serious updates to the deployment workflow, feature set, and documentation I would not recommend building your products on it.

simonpantzare 10y ago
They released proxy resources to API Gateway. Lets you specify a route like /foo/{path+} and all requests are forwarded as-is.
- davidjnelson 10y ago
  Great for simplifying universal web apps.
jotto 10y ago
The "0 to 1" workflow right out of AWS could not be easier, they have an in-browser code editor with a hello world already written for you. But that workflow doesn't make sense for real dev teams. So there's https://github.com/serverless/serverless https://github.com/serverless/serverless . It's driven by a yaml file and is intuitive. The only thing I'm bothered by is lack of environment variables (have to hard code them) and terrible API Gateway latency - see https://news.ycombinator.com/item?id=12681926 https://news.ycombinator.com/item?id=12681926 further down the page
- pmontra 10y ago
  For js projects you can work around that problem with const config = require('./config.json'); Then you do config.secrets.apiKey etc You have to gitignore config.json and include it in serverless.yml Other languages might have to read and parse that JSON into one of their data structures.
- joeyspn 10y ago
  Have you seen https://github.com/silvermine/serverless-plugin-write-env-vars https://github.com/silvermine/serverless-plugin-write-env-va...?
- gjolund 10y ago
  Serverless was nowhere near ready the last time I looked. Are they still requiring sn unrestricted iam profile? That is a non starter for most orgs. Also, I found working with serverless to be pretty unintuitive. You are relying entirely on large config files and it was very difficult and time consuming for me to test and rollback several different configs.
teej 10y ago
I'm in the same boat. I have 4 microscervices set up with API Gateway + Lambda and now actively guide people away from API Gateway.
- jeffbarr 10y ago
  Do you have any feedback that I can pass along to the team? Post it here or email it to me (email in profile).
  - hobofan 10y ago
    I'm in the same boat. If I would have to name one thing, it's that the configuration of API Gateway via the UI is unbearable if you have a nontrivial amount of routes (> 3). I need to configure Authorization, Error code mappings etc. for every route, although they are exactly the same. If there would be per-gateway defaults I can set with per-route overrides, that would cut down the setup time by 95%, which is the main thing holding me back from using API Gateway for projects that would suit it. Right now the only option I seem to have is using a tool like Terraform to automate it, which is a pain to adopt if you already have a running API Gateway.
    - aaimnr 10y ago
      You could also write a quick script using their REST API, although that's a bit cumbersome (lot of IDs that need to be passed around after creation of each resource). Still better than manual clicking in my opinion. http://docs.aws.amazon.com/apigateway/api-reference/resource/ http://docs.aws.amazon.com/apigateway/api-reference/resource...
    - imglorp 10y ago
      You might want to play with https://github.com/awslabs/chalice https://github.com/awslabs/chalice It gets you to hello lambda (python) in one shot, from the cli. Anything written down in one repo is going to be far more undertstandable than piles of hidden behaviors and obscure error messages. I think there's a new one on their blog for node.
ranman 10y ago
I'd recommend checking back in for a hot minute every few months or so. The development velocity on this service is pretty rapid. https://aws.amazon.com/blogs/aws/category/amazon-api-gateway/ https://aws.amazon.com/blogs/aws/category/amazon-api-gateway...

by gjolund 10y ago

simonpantzare 10y ago

They released proxy resources to API Gateway. Lets you specify a route like /foo/{path+} and all requests are forwarded as-is.

davidjnelson 10y ago
Great for simplifying universal web apps.

jotto 10y ago

The "0 to 1" workflow right out of AWS could not be easier, they have an in-browser code editor with a hello world already written for you. But that workflow doesn't make sense for real dev teams. So there's https://github.com/serverless/serverless https://github.com/serverless/serverless . It's driven by a yaml file and is intuitive. The only thing I'm bothered by is lack of environment variables (have to hard code them) and terrible API Gateway latency - see https://news.ycombinator.com/item?id=12681926 https://news.ycombinator.com/item?id=12681926 further down the page

pmontra 10y ago
For js projects you can work around that problem with const config = require('./config.json'); Then you do config.secrets.apiKey etc You have to gitignore config.json and include it in serverless.yml Other languages might have to read and parse that JSON into one of their data structures.
joeyspn 10y ago
Have you seen https://github.com/silvermine/serverless-plugin-write-env-vars https://github.com/silvermine/serverless-plugin-write-env-va...?
gjolund 10y ago
Serverless was nowhere near ready the last time I looked. Are they still requiring sn unrestricted iam profile? That is a non starter for most orgs. Also, I found working with serverless to be pretty unintuitive. You are relying entirely on large config files and it was very difficult and time consuming for me to test and rollback several different configs.

teej 10y ago

I'm in the same boat. I have 4 microscervices set up with API Gateway + Lambda and now actively guide people away from API Gateway.

jeffbarr 10y ago
Do you have any feedback that I can pass along to the team? Post it here or email it to me (email in profile).
- hobofan 10y ago
  I'm in the same boat. If I would have to name one thing, it's that the configuration of API Gateway via the UI is unbearable if you have a nontrivial amount of routes (> 3). I need to configure Authorization, Error code mappings etc. for every route, although they are exactly the same. If there would be per-gateway defaults I can set with per-route overrides, that would cut down the setup time by 95%, which is the main thing holding me back from using API Gateway for projects that would suit it. Right now the only option I seem to have is using a tool like Terraform to automate it, which is a pain to adopt if you already have a running API Gateway.
  - aaimnr 10y ago
    You could also write a quick script using their REST API, although that's a bit cumbersome (lot of IDs that need to be passed around after creation of each resource). Still better than manual clicking in my opinion. http://docs.aws.amazon.com/apigateway/api-reference/resource/ http://docs.aws.amazon.com/apigateway/api-reference/resource...
  - imglorp 10y ago
    You might want to play with https://github.com/awslabs/chalice https://github.com/awslabs/chalice It gets you to hello lambda (python) in one shot, from the cli. Anything written down in one repo is going to be far more undertstandable than piles of hidden behaviors and obscure error messages. I think there's a new one on their blog for node.

ranman 10y ago

I'd recommend checking back in for a hot minute every few months or so. The development velocity on this service is pretty rapid. https://aws.amazon.com/blogs/aws/category/amazon-api-gateway/ https://aws.amazon.com/blogs/aws/category/amazon-api-gateway...