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 :)
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!!
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.
Maximum time is 1 minute irrespective of developers preference. Functions are killed pretty well after the timeout period ;) Haven't tried to fill the memory though
Putting a time limit on a particular code processing is a piece of cake, not as hard as u r thinking. Otherwise I would have taken over the world till yet.
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?
I did that professionally. It was a bad idea. AWS will spin up a separate lambda for each parallel request. Then you start to deal with cold starts The main problem is that lambda can't route multiple parallel requests to 1 lambda. This is what kills the idea of a webserver on a lambda
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 ...
In times past, programmers were running code on their own computers to serve users of their applications. Now, they can store and run their code on Amazon's computers instead of their own.
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 :)
It was literally made by Amazon
@@mrmiked6577 there are many people that work at amazon :)
@@mrmiked6577 Who?
@@Patcul What are you asking?
agreed!
One of the few marketing videos that was clearly understandable to programmers, and without the marketing spiel
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!!
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.
Maximum time is 1 minute irrespective of developers preference. Functions are killed pretty well after the timeout period ;) Haven't tried to fill the memory though
Putting a time limit on a particular code processing is a piece of cake, not as hard as u r thinking.
Otherwise I would have taken over the world till yet.
can lambda have a HEV suit and kills combines
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?
I did that professionally.
It was a bad idea.
AWS will spin up a separate lambda for each parallel request. Then you start to deal with cold starts
The main problem is that lambda can't route multiple parallel requests to 1 lambda. This is what kills the idea of a webserver on a lambda
BEST EXPLAINATION VIDEO!
I'm taken by this. I read a book with similar content, and I was completely taken by it. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
- how this differs from old php-like hostings, heroku, etc?
- can I setup lambda on my server\OpenStack?
A. S. Lambda is just a fancy way to say serverless microservices. It scales automatically and only run when it is needed.
unlike php scripts you will be owned by amazon
We’re a big time AWS client here @ Chase Bank
Very nice video.
Simplicity much appreciated.
We're so glad you like it! 🙌
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 ...
Infrastructure abstraction. That's it.
Love this video! Do you mind me asking what software you used to produce it?
***** Thanks mate, I'll have a look at each of them. Any preferences yourself?
+Hadrian de Oliveira You reckon I could pull this off with something like Snap SVG?
AWS cinema toolkit
#justkiding
the voice of this narrator absolutely drives me insane... COMPLETELY INSANE - i don't know what to do
doesn't firebase already do this basically?
Maybe, but Firebase ain't AWS.
word up dawg
Great animation! :)
Skender
Very Nice Video. Good and Easy Explanation.
Does it run on a server?
The best explainer video. Thank you
Great video
You need to know Node.js, python or Java for compiling into lambda
How many developers know at least one of those languages? 85%+?
Y?
I think he's saying that Node, Python and Java are very common languages and that this won't be an issue
I know Node.js and basic python.
Admiring this breakdown? Dive deeper with the suggested read. "AWS Unleashed: Mastering Amazon Web Services for Software Engineers" by Harrison Quill
What’s the difference between AWS and the traditional web hosting for a simile web?
Auto scaling?
Well done with the video.
it was very useful, thank you
For some reason i am getting aperture science vibes from this video
i think Gordon Freeman would like this video
Soo good for neuro divergents to understand.
It’s easy to create a lambda function with cloud9!
Bring Ruby support please :)
I just think of Valve and Half life 😭
If you are looking for a tutorial with Python and Docker along with AWS Lambda, check this out: ua-cam.com/video/ehgvVZyfJfI/v-deo.html
good it is very useful
awesome!!!!!!!
excellent!!!
crt
very nice
Completed
Great vid but I still don't fully understand Lambda (not a programmer).
In times past, programmers were running code on their own computers to serve users of their applications. Now, they can store and run their code on Amazon's computers instead of their own.
Thanks.
Awesome!
AWS half-life
I hate the fact that you called this Lambda. It polutes the search space whe searching for lambda functions.
I'm sorry to hear this! 👋 Your feedback is important to us. 📋 I've passed your concerns along internally, for further review. 🤔 ^KR
such a robotic voiceover, very ingenuine and too irritating.
0:07 in-app purchases during a gaming session? Nope
‘Within a few seconds lambda will be ready” - dealbreaker?
You'll own no servers and be happy
oh looks like Lambda is going to make you lazy, it's Lambda lazy for you !
70254 Pfeffer Course