> Technologies such as HTTP/2, websocket and SSE are clearly pointing in the direction of long-running client-server interaction, yet current serverless solutio

> Technologies such as HTTP/2, websocket and SSE are clearly pointing in the direction of long-running client-server interaction, yet current serverless solutions have (to the best of my knowledge) no answer for that. This absolutely kills serverless for me: we are moving into a world where real-time interaction and updates are critical for serving our customers. HTTP/2, websockets, and SSE bring various benefits. Here are a couple of examples: - The potential for much improved user experience through greater application responsiveness, - Delivery of relevant data and insight, as and when it becomes available, without the need for clients to ask for it - again, for us that can deliver a much better user experience. These are nullified by (current implementations of) serverless.