- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Lambda can scale to handle traffic spikes much faster than EC2 autoscaling.
The first time you invoke your function, AWS Lambda creates an instance of the function and runs its handler method to process the event. When the function returns a response, it stays active and waits to process additional events. If you invoke the function again while the first event is being processed, Lambda initializes another instance, and the function processes the two events concurrently. As more events come in, Lambda routes them to available instances and creates new instances as needed.
The default regional concurrency quota starts at 1,000 instances. Let's say your function execution time is 10ms, this means you can handle 100,000 executions per second without requesting a quota increase.
https://docs.aws.amazon.com/lambda/latest/dg/invocation-scaling.html
Amplify will have no problem with huge traffic spikes, it is really just a wrapper around route 53, Cloudfront, and s3 so for static sites it is pretty much bomb proof.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 7 mesi fa
Thank you!