Exactly. I found serverless paradigm is particularly hard to implement stateful patterns. Even if there are some component could do that, most of them are trick

Exactly. I found serverless paradigm is particularly hard to implement stateful patterns. Even if there are some component could do that, most of them are tricky. One thing serverless architecture look like is a little bit of Erlang/BEAM. You can 1. Call a function to spawn a process. The function itself would be executed in that new process. 2. The process can hold a state and iterate in a recursive manner. 3. The process can expect a message, or send another process a message. And that's the minimalist way to build up something called Actor. With Actor and bi-directional protocols like WebSocket, you can achieve amazing dynamic stuff easily. Serverless, on the other hand, is mentally very similar to that paradigm. However, without the long-running process, single-direction messaging etc. There should be a huge potential lies ahead. All we need is a cloud operating system like Erlang/BEAM but a much bigger one at planet scale.