3 ms·

> the broker needs to be updated very infrequently, so it can have a gigantic uptime, and the backend PHP API gets updated all the time transparently with a git

> the broker needs to be updated very infrequently, so it can have a gigantic uptime, and the backend PHP API gets updated all the time transparently with a git pull I strongly advocate this architectural style. Even for developers well-versed in Node, Go, etc, it's good defensive programming to split the application into two processes (broker and backend). You might find the Pushpin project interesting. It's an attempt at generalizing the broker part, and it works great with a stateless PHP backend.

Udo 11y ago
It's great to see I'm not alone :) > You might find the Pushpin project interesting. That is interesting, I didn't know such a project existed (kinda surprised actually). However, that's not a pain point for me at the moment. I maintain my own reusable broker module for Node/Websocket things, plug it into the NginX config and I'm ready to go. Plus it's not too hard to cook up one of these things if the need arises.