Faye VS Pushpin

Faye WebSocket is a versatile WebSocket implementation derived from the Faye project. Faye is a messaging system that uses the Publish/Subscribe model and the Bayeux protocol. It provides message servers for Node, Ruby, and all major web browsers. - Source: dev.to / 6 months ago

I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution? Source: about 3 years ago

For realtime, I used Pushpin with Server Sent Events. (It supports WebSocket as well). - Source: dev.to / 10 months ago

Instead of letting clients directly interface with your services over websockets, consider using Pushpin [1], which allows you to completely isolate realtime communication from your services. As a bonus, it also provides you the ability to cycle (redeploy/restart) your services without your clients having to reconnect (that's where the name comes from). And as you can imagine - because communication with your... - Source: Hacker News / 11 months ago

Vapor[0] based on Swift. Advantage of this is that you don't have to evaluate multiple frameworks for Swift and suffer paralysis by analysis. All the Swift community is behind one framework. The next is Actix[1] based on Rust. There are many frameworks in Rust and most of them have not reached 1.0 And which framework will survive becomes a question. Other not so well-known is Wt[2] based on C++. This actually is... - Source: Hacker News / over 1 year ago

If you are developing the backend then Pushpin[0] is the easiest to integrate with. [0] https://pushpin.org. - Source: Hacker News / over 1 year ago

There is also the option of running a proxy which handles the stateful nature of websockets (i.e. https://pushpin.org/), and then handle the rest in a stateless way with lambdas or similar. Source: over 1 year ago