[furstenheim]

One thing that bothers me about serverless functions is that there is virtually no concurrency. Once you return you have no assurance that your code will keep on working.

If you want to perform actions that might be throttled (cloudwatch for example) and are not critical for the response, you cannot have a singleton processing them after you return, because they might not be processed.

[k__]

Isn't this more a queue than a FaaS problem?

[redisman]

How could it be orchestrated by the cloud if there's no clear end to your workload?

[furstenheim]

Of course, I'm not saying the opposite. But you're sacrifying development options in the process