Introduction to AWS Lambda - Serverless Compute on Amazon Web Services

AWS Lambda is a compute service that runs your code in response to events and automatically manages the compute resources, making it easy to build applications that respond quickly to new information. Learn more:


37 thoughts on “Introduction to AWS Lambda – Serverless Compute on Amazon Web Services”
  1. One of the few marketing videos that was clearly understandable to programmers, and without the marketing spiel

  2. For a person like me who's a non-tech or no hands on experience the visuals and simple explanation matters the most. Not the core details or a walk through the AWS console. I will always remember this kind of best videos. You know what the duration of the video < 5 minutes matters the most. And you made it!! Thank you!!

  3. Is Serverless computing only for purposes like these micro services? Or, is there an option like hosting an entire web application in serverless environment, so that it auto scales depending on traffic?

  4. I don't get this: with or without lambda, the service needs a code itself . So what is the difference with server or with lambda ? still needs the code anyway …

  5. This is genuinely a really well made (and written) video. I feel like I could show non-tech people this and they'd walk away with the gist – if not all the specifics – of what Lambda functions do. Kudos to the group that made this 🙂

  6. This video… is pretty cute. One thing about Lambda is how well it runs untrusted code. For example, if you provision an arbitrary lambda function to run with 128MB and 1 compute unit, with a timeout of 3 seconds, it is possible for the function to eat up resources beyond the limits, and is it possible to get charged if the function doesn't respond to a kill signal at 3 seconds?

    For example, a malicious function might run an intense CPU task which might take long for AWS to kill. If AWS's kill signal is not implemented well, is the developer charged for the spillover in resource and compute time? What if the untrusted function writes megabytes of data to the system.out, and you have logging enabled? Are there easy ways to mitigate these types of attacks? Will the developer be forced to parse out any system.out statements in untrusted code?

    As a developer, if I set a timeout for 3 seconds, there's no way I would want to pay for 20 minutes if the function stopped responding. This is one potential concern for using Lambda. It would be nice if AWS addressed these concerns.

  7. – how this differs from old php-like hostings, heroku, etc?
    – can I setup lambda on my serverOpenStack?

Leave a Reply

Your email address will not be published.

Captcha loading...