[korzun]

Maybe I'm looking at this from a different perspective. Some implementations do not require any response.

For example if I have a honey pot that collects random events, the clients can just send the data to it without expecting a result (IE: I don't care if it's successful or not) and honey pot is not expected to write any sort of response.

Clients send data and move on.

[zhong-j-yu]

I agree, async is needed sometimes. Another example, a server broadcasts an event to multiple clients (e.g. a chat app), it would be silly to spawn a thread per client for that.

[korzun]

But the whole point of async is that, after data is dispatched the client moves on. I'm not sure what NodeJS does with it but this is my interpretation of the concept.

I don't think people who know what they are doing, use async calls for mission critical operations.

If async call returns response and client is required to read the response it's no longer considered non-blocking from technical perspective.

[syntheticlife]

Or, sometimes you have to serve 10k pages at once. http://www.kegel.com/c10k.html