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
This may not be what you are looking for, but why not use a combination of Postgres listen/notify and PushPin[0] to support push notifications? [0] https://pushpin.org. - Source: Hacker News / over 1 year ago
Could use pushpin[1] and have several fallbacks, like SSE -> Websocket -> polling. [1]https://pushpin.org/. - Source: Hacker News / about 2 years ago
Have you looked at Pushpin [1]? (disclosure: I'm the lead dev). The goal is to be able to drop it in with anything, rather than requiring a certain language. [1] https://pushpin.org. - Source: Hacker News / almost 3 years ago
> why to have thousands of connections instead of a single one (or a bunch) that simply forwards websocket packets with some "connection id" For anyone wanting to do this sort of thing, check out Pushpin [1]. It's a proxy server that can manage WebSocket connections on behalf of any HTTP backend. There are middleware libraries (such as [2]) to make it easy to write handler code. Disclosure: lead dev. Came up with... - Source: Hacker News / about 3 years ago
Do you know an article comparing Pushpin to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Pushpin. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.