Full Guide to Developing REST API’s with AWS API Gateway and AWS Lambda • Hacker News Board

Re: Full Guide to Developing REST API’s with AWS API Gateway and AWS Lambda

#41

Post by davidjnelson » Mon, May 14, 2018, 11:51 PM UTC

nstj wrote: post #40

davidjnelson wrote: post #37

I wonder if I'm missing something. Given 10 minutes of load for pre warming, I was getting 95th percentile times of 1.6 seconds with a bare minimum node lambda hello world function. I threw 1,000 concurrent requests at it across 4 threads, with a 1,000 concurrent execution limit configuration on aws. I was really excited about lambda, but that is flat out terrible performance for a lot of users. Is this not an issue…

My results have been similar.

Given that, I wonder why people keep writing about it? I get the appeal for an internal app or a background job, but for a public facing rest/graphql api? Seems like the performance isn't there.

Re: Full Guide to Developing REST API’s with AWS API Gateway and AWS Lambda

#42

Post by jcims » Tue, May 15, 2018, 12:01 AM UTC

matchagaucho wrote: post #33

dayjah wrote: post #23

IME the AWS GUI is not useful for all that much in a meaningful context. Thus this post is pretty misleading to a new person getting involved in cloud; it doesn’t qualify as “full” in my mind. As a number of other comments have pointed out, there are packages that help with managing your infrastructure in code; which is critical outside of anything other than a play environment. Terraform, serverless, cloudformation,…

My experience... while Lambda is capable of hosting micro-services, any coding pipeline that emphasizes continuous integration (CI) will be better served with one, generic, monolithic Lambda function that dispatches to sub-modules behind the scenes. However, this only scales up to a 50MB binary distributable.

This probably wouldnt be the case if you could just add decorators to the methods you want exposed as functions.

Re: Full Guide to Developing REST API’s with AWS API Gateway and AWS Lambda

#43

Post by mart187 » Tue, May 15, 2018, 5:45 AM UTC

There is no remark that an admin IAM user should not be used. This is highly critical and should not be done ever.

Also using something like serverless framework is better suited for the average developer to get this setup up and running. Clicking through the aws cli is not something professional aws users do often. (exceptions would be Cloudwatch metrics and logs). The article should at least mention that infrastructure better is managed in code.