AWS Lambda Concurrency | Reserved Concurrency | Provisioned Concurrency
ฝัง
- เผยแพร่เมื่อ 15 ก.ค. 2024
- With AWS Lambda you can enable concurrency for the request that you want to provision.
⭐ Kite is a free AI-powered coding assistant that will help you code faster and smarter. The Kite plugin integrates with all the top editors and IDEs to give you smart completions and documentation while you’re typing. I've been using Kite for 6 months and I love it!
www.kite.com/get-kite/?...
For this AWS lambda provides 2 types of concurrency:
Reserved and Provisioned, and we will discuss them one by one.
In AWS lambda in order to ensure that a function can always reach a certain level of concurrency, we can actually configure the function with reserved concurrency.
Concurrency is the number of requests that your function is serving at any given time. So lambda has your function that you have written and uploaded and if a single user makes a call to the function, it is considered to be a single request.
So the number of requests that your function is serving at any given time, we consider that as concurrency.
Timelines for your convenience:
00:00 // Intro
00:32 // What is AWS Lambda Concurrency? What is Reserved Concurrency?
06:46 // What is Provisioned Concurrency?
10:10 // Functional Scaling for Provisioned Concurrency?
12:20 // Provisioned Concurrency pricing model
17:00 // Outro
AWS Solutions Architect Associate Certification 2020 Playlist:
tinyurl.com/y4lr8zu4
Please follow we in the links below to stay updated: 🙌
🍀Click on the link below to subscribe: tinyurl.com/qqebnwz
🍀Instagram: / tougherapollo
🍀Twitter: / tougherapollo1
🍀Discord: / discord
🍀Care to share: / pythoholic
Disclaimer: The content provided in the channel are not affiliated in any way to the organization. We provide information here on the channel based on the knowledge we have on the topic. We advise our viewers to please do their own research and read more about them from the source provided by the organization to get a better outlook on the topic that has been covered.
These videos are just to provide you a platform to learn, and there can be mistakes and we are always trying to improve based on your feedback. we recommend viewers to have an open mind. Please support the channel to get more content like these in the future.
#AWSLambdaConcurrency #AWSSolutionsArchitectAssociate2020 #ProvisionedConcurrency - วิทยาศาสตร์และเทคโนโลยี
Timelines for your convenience:
00:00 // Intro
00:32 // What is AWS Lambda Concurrency? What is Reserved Concurrency?
06:46 // What is Provisioned Concurrency?
10:10 // Functional Scaling for Provisioned Concurrency?
12:20 // Provisioned Concurrency pricing model
17:00 // Outro
Theoretical content is good, but we need hands-on models for better understanding.
I hope you will provide hands-on on all services asap.
Sure, thanks for the feedback.
@pythoholic What sort of questions can be expected from this section?
Are the label in the page provisioned concurrency pricing wrong? from top to bottom is unresearved, throttling, provisioned and researve instead of unresearved, throttling, researved and provisioned.
Question:
I do have python script that scrapes data from a real estate listing website.
After few requests I got my IP blocked, one way to overcome the restriction is to implement proxy rotation so the site does not know that all the requests are made by the same machine, but what about using lambdas?
If I do configure a lambda that does this requets, and concurrently execute it 1.000 times, would the target website interpret that there are 1000 different machines requesting data or, would interpret that just one machine is making 1.000 requests?
Thanks!
The answer to this lies in the concept of how a request is processed by the server. Let suppose you make use of an API and perform 1000 API calls to perform a load testing. If you are a API developer you know that each call is considered as a single request. The request context doesnt necessarily have to define if its from the same machine. You need to just serve the request. The target machine which serves the request only thinks of how to serve it with a response without having to worry about if that request comes from a single or different machine until and unless there is a condition block that captures information of the requester and has to serve response based on that. i hope you got the idea.
The point where we want to make sure our request doesnt get blocked if sent from the same machine is basically due to the session and its metadata. If you want to have it tested -- create batch processing with lambda and see if the request are blocked.
@@Pythoholic Interesting, imagine I batch 1000 requests to an API endpoint using my computer by previously setting up the headers of the requests to mimic the ones a normal web browser sends.
Since is not possible for a human to consume this amount of data at the same time, got discovered and IP blocked.
One way to overpass this might be to batch using 1000 unique IPs, one per request.
I suspect that when concurrently working each Lambda is executed on a unique AWS machine hence each request is sent from a unique IP.
Easiest way to check is what you suggested, batch and see, I just don't have any server running but I will try one day or another.
Are these topics - Reserved Concurrency & Provisioned Concurrency, important for exam prospective?
Yes, for the solution architect it is
great content
but could you please upload the hands on demo ?
Hi there is a demo on the playlist for aws solution architect please have a look
@@Pythoholic subscribed your channel 😅
Function is throttled
Your function cannot be invoked while the reserved concurrency is zero.
i make 200 then it works