Serverless

concurrent executions" VS  requests per second

It's not a one-to-one translation. in this case its a FAAS( Lambda ) 

Concurrent executions only tells you how many instances of Lambda functions are running at once. It doesn’t tell you how many requests per second you can push through those instances.

If your function averages 100 ms per request, then every instance of this function can handle ~10 requests per second. Because a Lambda function can go from 0 to 1,000 concurrent executions instantly (since 2023), that’s roughly 10,000 RPS of burst capacity!

And you do't pay for any of that headroom when your traffic is sitting at 5 RPS. But it doesn't stop there. It can add another 1,000 concurrent executions every 10 seconds. After a minute, you can have 7,000 concurrent executions.

At 100 ms latency, that’s about 70,000 RPS.   That's plenty for even aggressive traffic spikes!

The main limiter is your account-level concurrency. New AWS accounts start with a region-wide limit of just 10 concurrent executions.