Serverless lessons learned #3 reserved concurrency

1. Reserved Concurrency ? Serverless on AWS lessons learned #3 Are you really production-ready?

2. The default limit for concurrent lambda executions is 1’000 per account. 1’000 332 executions limit

3. When this limit is reached, new lambda invocations will be rejected. 1’000 executions limit

4. This is called Rate Limiting: an important concept in distributed systems. TooManyRequestsException Rate limit exceeded

5. Where is the problem?

6. Out of the box, all lambdas share the same 1’000 executions. 1’000 All

7. One lambda function may consume a lot concurrent executions and impair the whole system! rest 1 bursting Lambda 999

8. How to prevent?

9. Setting the reserved concurrency option for each system-critical lambda function will ensure separated execution limits. *more details in the description

10. 700 332 rest 200 system critical lambda 98 100 bursting lambda

11. Reserved Concurrency

12. thumbs up, comment, share What are your thoughts? Is anything important missing? If you liked it, please leave a comment. connect with me!

Serverless lessons learned #3 reserved concurrency

More Related Content

What's hot (18)

Recently uploaded (20)

Serverless lessons learned #3 reserved concurrency