AWS re:Invent 2022 - A closer look at AWS Lambda (SVS404-R)

[@jlkinsel]

Here's that 5⭐ rating - love the 400 level talks!

[@Qwerty20238aw]

One of the best re:Invent sessions I have watched this year! 🎉

[@alexanderkosarev9915]

I had some expectation for complexity behind AWS Lambda, but never had time to get deep into it. This hour was one of the best spent on re:Invent 2022! Bravo for speakers!

[@KishoreJonnalageddaTMNA]

Great job describing the journey of lambda and how it is optimized, not only in storing the executable environment but executing it across AZs.

[@rigasakhairan7717]

Nice to everyone 🙋‍♀Hi Great to see you From Nigeria 🕊🇳🇬

[@ruoxuan666]

Thanks your so much. Awesome. It really helps me a lot on how to build complex and flexible system!

[@randomtalks4304]

In this talk, the speaker discusses AWS Lambda and how it has evolved since its launch eight years ago. The speaker highlights how Lambda is the fastest way to build modern applications with the lowest total cost of ownership, and how it helps teams focus on their code instead of infrastructure management. The speaker also discusses some common areas where customers see benefits from using Lambda, such as IT automation, data processing pipelines, and building microservices-based applications. (Thank you - ChatGPT)

[@randomtalks4304]

here are some additional highlights from the talk: AWS Lambda was launched eight years ago at the re:Invent conference and has since seen more than a million customers build applications with it. Lambda continues to grow at a rapid rate and is used in a variety of applications, including IT automation, data processing pipelines, and machine learning. The Lambda team has done a lot of innovation to make the service more powerful while also keeping it simple to use. The speaker discusses the different Lambda invocation models and how they work, including synchronous and asynchronous invokes. The speaker also talks about some of the challenges the Lambda team has faced and how they have solved them, such as scaling up with provision concurrency and supporting new event sources. The speaker concludes by discussing some of the exciting new features and improvements that are coming to Lambda, including support for custom runtime, improved cold start performance, and more.

[@randomtalks4304]

@Kekeh take the transcript and ask it to summarize 🙂

[@ianokay]

Is that not too many tokens? Do you have to break it up into multiple prompts?@@randomtalks4304

[@derekreed6798]

I love the idea of lambda but how are AWS keeping down the cost to the customer, for Lambda (esp after finding it internally not cost effective)? 9:11 - eventbridge

[@awssupport]

Hi Derek! 👋 We have a great document and blog posts for cost optimization with AWS Lambda: Here's the doc: go.aws/3tSUM0z. These are the blog posts: go.aws/3skQYF3 👈 and here: go.aws/47gGwx6. 🤝 ^RW

[@ShekharSuman271991]

at around 31 mins its explained that the containers are not fully loaded in the MicroVM but only chunks of it (which is enabled by how lambda chucks and stores a container) - but how does lambda identify which container chunks to pull on a certain function invoke?

[@awssupport]

You may find this resource helpful, Shekhar: go.aws/3Y2ubrO. 📄 However, this is an excellent question for our re:Post platform! Our community of experts may be able to assist you with further guidance: go.aws/aws-repost. 📮 ^TE

[@brijeshmondal_]

Just wow🤟

[@amazonwebservices]

😀 👍

[@yekohein1528]

Hello Julian!

[@JagaSantagostino]

Very interesting!

[@teokostadinov]

Awesome!

[@dkomarnickiit]

Very cool

[@ramkundala4925]

Simplified complex problem

[@arkadiyshuvaev]

AWS injects more and more marketing into tech videos :( I want to see more technical details and do not want to watch Coca-Cola success story

[@Rickety3263]

How embarrassing to be forced to use a suffix like “(he/him)” instead of a proper “Mr.” How cringe