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

A shared file system for lambda functions

aws.amazon.com

Post reply on HN
Print view View original

61–70 of 113 posts

Re: A shared file system for lambda functions

#61

Post by vosper »

somurzakov wrote: post #43
Thorentis wrote: post #29

Cool, so we're staring to curve more sharply around the full circle we'll eventually go on. So now lambda functions can mount persistent block storage. Next up: allow your lamda functions to run for longer Then: allow multiple lamda functions to execute concurrently, and indefinitely, as a group, while having block storage mounted And finally: use your EC2 instances as lambda functions

cron+perl on a shared hosting is a lambda from 90s, cheap, fast, and it just works

Lambda is free cron, unless you need a lot of jobs

Re: A shared file system for lambda functions

#62

Post by philliphaydon »

redis_mlc wrote: post #49
VWWHFSfQ wrote: post #42

I'm curious what people actually use Lambda for? I tried Lambda for a use-case that I had in 2018: We published Polls and Predictions to people watching the 2018 World Cup. We set the vote callback URL to a function on AWS Lambda. It failed spectacularly during our load-testing because the ramp-up period was far too slow. We needed to go from 0 to 100,000 incoming requests/second in about 20 seconds. We had to switch…

AWS lambda is used in 2 categories: 1) AWS administration-related actions (required for non-trivial mgmt.) 2) end-user actions (optional). AWS throttles and limits everything, so expecting 100,000 requests in 20 seconds on a default AWS account is unreasonable. The Cloud doesn't mean unlimited capacity. Also, I haven't seen anybody version control lambda code, even in compliance environments, so something to investig…

> Also, I haven't seen anybody version control lambda code, even in compliance environments, so something to investigate.

Huh, how is it any different building and deploying to anything else.

I store the code in git, build it in team city, and deploy it to S3 using octopus deploy which updates the lambda to point to the new versioned off zip.

Re: A shared file system for lambda functions

#64

Post by paloaltokid »

VWWHFSfQ wrote: post #42

I'm curious what people actually use Lambda for? I tried Lambda for a use-case that I had in 2018: We published Polls and Predictions to people watching the 2018 World Cup. We set the vote callback URL to a function on AWS Lambda. It failed spectacularly during our load-testing because the ramp-up period was far too slow. We needed to go from 0 to 100,000 incoming requests/second in about 20 seconds. We had to switch…

I consult and have encountered many people who build data intake pipelines using Lambda. The most common pattern is to have Lambdas feeding into a data lake somewhere, often Redshift.

It is a very common pattern for IoT applications also and well-suited for it. The workloads are often bursty and unpredictable.

But for many things, I believe it is still preferable to stick with a traditional web app or API. It is still early days for serverless and there is a lot of hype around it. As with most hyped things, people see it as a silver bullet and don't think through the tradeoffs they are making.

Re: A shared file system for lambda functions

#65

Post by arcturus17 »

zelphirkalt wrote: post #63

"lambda functions" not "lambda expressions" - It is funny (or not) how Amazon redefines how a term is used by naming a product. The words actually make no sense, but people do not care and say It anyway "lambda function".

I just glanced over the Wikipedia article for lambda calculus and there is at least one mention to “lambda functions”, right in the intro.

What’s wrong with “lambda functions”?

Re: A shared file system for lambda functions

#66

Post by Konohamaru »

This is misdirection by naming, like how University of Phoenix is similar to Arizona State University, Phoenix. "Lambda functions" sounds like anonymous functions, but is actually referring to a proprietary interface to AWS Lambda™. They named it this way so that readers confuse AWS Lambda™ for programming lambdas.

Re: A shared file system for lambda functions

#67

Post by garethmcc »

Konohamaru wrote: post #66

This is misdirection by naming, like how University of Phoenix is similar to Arizona State University, Phoenix. "Lambda functions" sounds like anonymous functions, but is actually referring to a proprietary interface to AWS Lambda™. They named it this way so that readers confuse AWS Lambda™ for programming lambdas.

If anyone is initially fooled by the naming that illusion is broken very quickly after just a few seconds of looking into it so I doubt that this was an intentional act to trick people

Re: A shared file system for lambda functions

#68

Post by QuinnyPig »

Konohamaru wrote: post #66

This is misdirection by naming, like how University of Phoenix is similar to Arizona State University, Phoenix. "Lambda functions" sounds like anonymous functions, but is actually referring to a proprietary interface to AWS Lambda™. They named it this way so that readers confuse AWS Lambda™ for programming lambdas.

One of AWS’s core competencies is being bad at naming things.

Re: A shared file system for lambda functions

#69

Post by Konohamaru »

garethmcc wrote: post #67
Konohamaru wrote: post #66

This is misdirection by naming, like how University of Phoenix is similar to Arizona State University, Phoenix. "Lambda functions" sounds like anonymous functions, but is actually referring to a proprietary interface to AWS Lambda™. They named it this way so that readers confuse AWS Lambda™ for programming lambdas.

If anyone is initially fooled by the naming that illusion is broken very quickly after just a few seconds of looking into it so I doubt that this was an intentional act to trick people

Lots of companies do what Amazon does. See University of Phoenix vs. ASU Phoenix campus.

Is it stupid? Yes, but advertising is generally geared toward human stupidity. More specifically, it's geared toward pointy-haired bosses who are being presented AWS Lambda™ who are thinking to themselves "well I heard a lot about lambdas, are these what my team meant?"

Re: A shared file system for lambda functions

#70

Post by tlarkworthy »

philliphaydon wrote: post #60
VWWHFSfQ wrote: post #42

I'm curious what people actually use Lambda for? I tried Lambda for a use-case that I had in 2018: We published Polls and Predictions to people watching the 2018 World Cup. We set the vote callback URL to a function on AWS Lambda. It failed spectacularly during our load-testing because the ramp-up period was far too slow. We needed to go from 0 to 100,000 incoming requests/second in about 20 seconds. We had to switch…

I recently built a facade for payment gateway callbacks to put message into SQS to reduce loss of requests from main API. (Costs less than $1 per month to handle all requests and # of lost requests in the last 6 months has gone from ~15 out of ~10k to 0) Edit 5 months cos it went live in jan.

I do the exact same! I call it write ahead logging in the proxy: https://futurice.com/blog/openresty-a-swiss-army-proxy-for-s...
Post reply on HN