3 ms·
One example that I think fits very well is a websocket server. As you often have a large number of clients with long-running connections and relatively low-volu
by meritt 9y ago
One example that I think fits very well is a websocket server. As you often have a large number of clients with long-running connections and relatively low-volume bidirectional communication, a single process running react/amp can easily handle hundreds or thousands of clients.
The majority of the examples out there are indeed contrived and better suited to a queue system as you've described.
- jrs95 9y agoI’ve seen approaches that basically use a Node server + queues for this. I think this is how Laravel does websockets.
- francislavoie 9y ago+1 to this. I like Ratchet for websockets written in PHP. One nice thing is that I can share certain things like session code between my websocket server and my backend framework. Having both be in the same language, in the same project, makes things a lot cleaner for me.