Made a Stack Using AWS API Gateway, AWS Lambda, and Swagger and Want to Share

5 points by megazoo ↗ HN
Hey, all. I recently transitioned to a new type of stack using Swagger, AWS Lambda and the new AWS API Gateway and it rules so I’ve put it together in a stack and I’m going to do a live video about it…

It works like this: You define your API in JSON (Swagger), deploy it instantly using AWS’s API Gateway, and write an AWS Lambda function for each API route.

This way, the code for each API route only runs when it’s called. Which is cheaper than paying for a 24/7 web server. Plus, the code for each API route is totally isolated from all other routes so it’s easier to fix stuff rapidly without affecting anything else, and when code breaks, it only affects one API route!

I think this is going to be the new normal for start-ups. If this sounds cool to you, I’m going to do a live stream this Sunday, July 26, at 5pm PT @ https://www.livecoding.tv/ac360/. The video will be recorded and available at that link as well (and possibly Youtube).

1 comment

[ 3.9 ms ] story [ 11.4 ms ] thread
Sounds good... I want to know a thing as I understand AWS Lambada thing, is you code your own function for each API, could I use total cli app instead and use one of its functionality... For example if I want to use imagemagik can I use it instead of my own function or not?