This isn't a serverless specific question, but i suspect this right audience to chime in....
I was wondering if non-blocking I/O matters much less(not at all?) in a serverless world?
My feeling is that it really doesn't matter. However, i'm basing this on the my understanding that the lambda/azure/google functions service one and only one request at a time. I'm wondering if its safe to assume this will always be true.
If so, from a programming model, doesn't that imply that any time spent waiting for I/O, can never be used to service another request, because you'll never get one routed to you until you exit?
I can only think that if there were some way to spawn child threads doing I/O inside your function, you'd benefit from using the wait time. I know spawning threads in the JVM is doable, pretty sure it is in python, and i think it's impossible in node, but not sure.
Can someone confirm, clarify, enlighten me?