Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Lambda Makes Serverless Applications a Reality

techcrunch.com

Post reply on HN
Print view View original

41–50 of 55 posts

Re: AWS Lambda Makes Serverless Applications a Reality

#41

Post by bolchevich »

yeukhon wrote: post #25
count wrote: post #16

Earlier quoted context omitted.

Can you mount an EFS on the lambda instance (I don't know, but that comes to mind as a possible solution), possibly via a java NFS daemon or something in userspace?

I have never done that before but I imagine no, you are not supposed to have access to the operating system and know where the instance is. Similar to SNS and SQS, you don't get an IP of your SQS. I could set up an EC2 instance with some storage, but that goes back to my current design. If you do get that IP :-) contact AWS. That's probably a million dollar vulnerability. I'd suppose underneath they run container/lxc…

It's an EC2 instance running inside a VPC using a custom Amazon Linux that uses some LXC trickery to contain your process. In theory EFS is possible.

Re: AWS Lambda Makes Serverless Applications a Reality

#42

Post by nickspacek »

cdnsteve wrote: post #38

I just ended up using Heroku for an API instead. I was able to use the latest language version and microframework of my choice and still not worry about servers. Setup was way more intuitive than AWS. Testing locally was a known thing and easy. I found wrapping my head around testing API gateway to lambda to aws services a mess. Also all the IAM rules got confusing. I'll probably have another look after it has mature…

Heroku is more like Elastic Beanstalk than Amazon API Gateway. API Gateway is more of a Backend As A Service as I understand it, like Parse.

Re: AWS Lambda Makes Serverless Applications a Reality

#43

Post by daviding »

epoch1970 wrote: post #24

How does one version control the scripts and easily deploy them? How does one test them on one's own computer when developing them? Must the scripts be uploaded into AWS after every change if testing is to be done?

I use this to run/test locally, and then deploy. I also upload binaries, so do use the AWS upload but it's quick via a script within the deploy helpers.

https://github.com/motdotla/node-lambda

Re: AWS Lambda Makes Serverless Applications a Reality

#44

Post by zbjornson »

Has anyone using Lambda gotten Amazon to substantially increase the limits on concurrent jobs? We asked for 10k and they gave us 1k. The article posted in this thread and other sites use words like "limitless" and "massive," but 1k concurrent requests is ... tiny. We're hesitant to keep building around this architecture because of the limit.

Re: AWS Lambda Makes Serverless Applications a Reality

#45

Post by andrewmunsell »

nickspacek wrote: post #42
cdnsteve wrote: post #38

I just ended up using Heroku for an API instead. I was able to use the latest language version and microframework of my choice and still not worry about servers. Setup was way more intuitive than AWS. Testing locally was a known thing and easy. I found wrapping my head around testing API gateway to lambda to aws services a mess. Also all the IAM rules got confusing. I'll probably have another look after it has mature…

Heroku is more like Elastic Beanstalk than Amazon API Gateway. API Gateway is more of a Backend As A Service as I understand it, like Parse.

API Gateway doesn't really encompass Parse's scope, either. It's more of a router-as-a-service that allows you to forward HTTP requests to other AWS services, Lambdas, or your custom backend (+ do some stuff with IAM and auth, etc)

Re: AWS Lambda Makes Serverless Applications a Reality

#47

Post by RA_Fisher »

twagner wrote: post #31
yeukhon wrote: post #12

If Lambda is able to expand the /tmp disk space from 500MB to a few GB I think that will further make the adopter better on my end. I have a requirement in which Lambda is a perfect solution except the disk space is not enough. Of course I can further divide the work into smaller chunks. If you have use distributed task library like Celery, just think of that no longer tie to your application, and you can run on even…

Appreciate the feedback/suggestions! We'll take a look at expanding the disk space, probably as part of the "power level" adjustment that already affects memory, CPU power, etc.

One minor feature request would be to allow Scheduled Events every minute. My current solution is EC2 -> S3 file every minute, but it's a kludge.

Re: AWS Lambda Makes Serverless Applications a Reality

#48

Post by x5n1 »

imglorp wrote: post #34
posabsolute wrote: post #3

It's funny we tested lambda + Amazon gateway api this week at work. It's awesome!.. Until you have to deal with the cold start issue. Our first call takes about 1.5 seconds; and then all other calls take about 50-80ms. Your container stays in cache about 5-10 minutes unless it is called back, there are no guarantees. This micro service is not called often and for us 1.5 seconds is never acceptable.

Our issue was price. Boss did the math for our use case, around a million hits/sec 24/7, and it worked out to billions of dollars. We're building a solution (on aws) for a little less than that.

It's good the boss can do that sort of math. That's why you need him and why he is called the boss.

Re: AWS Lambda Makes Serverless Applications a Reality

#49

Post by yeukhon »

RA_Fisher wrote: post #47
twagner wrote: post #31

Earlier quoted context omitted.

Appreciate the feedback/suggestions! We'll take a look at expanding the disk space, probably as part of the "power level" adjustment that already affects memory, CPU power, etc.

One minor feature request would be to allow Scheduled Events every minute. My current solution is EC2 -> S3 file every minute, but it's a kludge.

There is : http://www.slideshare.net/AmazonWebServices/cmp407-lambda-as... but I kinda dislike the whole complexity). This is a new feature.

Re: AWS Lambda Makes Serverless Applications a Reality

#50

Post by eistrati »

x5n1 wrote: post #48
imglorp wrote: post #34

Earlier quoted context omitted.

Our issue was price. Boss did the math for our use case, around a million hits/sec 24/7, and it worked out to billions of dollars. We're building a solution (on aws) for a little less than that.

It's good the boss can do that sort of math. That's why you need him and why he is called the boss.

Why do I have a feeling that you are the "boss" in this picture? :)
Post reply on HN