<story><title>A shared file system for  lambda functions</title><url>https://aws.amazon.com/blogs/aws/new-a-shared-file-system-for-your-lambda-functions/</url></story><parent_chain></parent_chain><comment><author>VWWHFSfQ</author><text>I&amp;#x27;m curious what people actually use Lambda for?&lt;p&gt;I tried Lambda for a use-case that I had in 2018:&lt;p&gt;We published Polls and Predictions to people watching the 2018 World Cup.  We set the vote callback URL to a function on AWS Lambda.&lt;p&gt;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&amp;#x2F;second in about 20 seconds.&lt;p&gt;We had to switch to an Nginx&amp;#x2F;Lua&amp;#x2F;Redis endpoint because Lambda was just completely unusable.  It would have cost us $27,000&amp;#x2F;month to pre-provision 10,000 concurrent executions...&lt;p&gt;What is it that people actually use Lambda for?</text></comment>
<story><title>A shared file system for  lambda functions</title><url>https://aws.amazon.com/blogs/aws/new-a-shared-file-system-for-your-lambda-functions/</url></story><parent_chain></parent_chain><comment><author>scandox</author><text>Serverless is a bit like Stone Soup [1]. This I guess is the point at which the Tramp says: &amp;quot;Now if you just add a few onions it really helps the flavour...&amp;quot;&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.m.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Stone_Soup&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.m.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Stone_Soup&lt;/a&gt;</text></comment>