A shared file system for lambda functions • Hacker News Board

Re: A shared file system for lambda functions

#111

Post by giorgioz » Fri, Jun 19, 2020, 4:15 PM UTC

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…

at waiterio.com we use it for plain old web services. Essentially one service = one lambda Like a dyno on Heroku but much cheaper and much more scalable We used the Serverless Framework until few months ago and now we are migrating to AWS CDK

Re: A shared file system for lambda functions

#112

Post by giorgioz » Fri, Jun 19, 2020, 4:15 PM UTC

jupp0r wrote: post #13

This is a horrible idea. This gives lambda functions shared mutable state to interfere with each other, with very brittle semantics compared to most databases (even terrible ones).

time will prove you very wrong

Re: A shared file system for lambda functions

#113

Post by twoodfin » Fri, Jun 19, 2020, 6:23 PM UTC

staticassertion wrote: post #110

shoo wrote: post #109

Earlier quoted context omitted.

back when i was working on this (for a large org) they regarded anything in AWS as fundamentally lower trust than their own on-premises corporate networks, so there was a security requirement to do encryption in transit for all TCP connections -- this was for an application within the VPC with no public traffic

It's gonna depend on your threat model ultimately. Hard to imagine running on AWS if you don't trust them though.

It's not so much about trusting AWS not to pry into your data. More that the attack surface of your data as presented to AWS' other—potentially hostile—customers is (presumably) significantly reduced by not having the bytes flying around AWS' infrastructure in the clear.

To put it mildly, Amazon has a lot more folks a lot smarter than me thinking about these tradeoffs, so I assume they had good reason to think it was fine the first time around. I'm just surprised that the state-of-the-art for cloud-hosted services doesn't presume building on TLS from day 1, so I'd love to know what those reasons are.