deepstream.io VS Pushpin

What your trying to do is very difficult (particularly since your data views are relying upon joins and group queries.) You may need layered solutions. I've been looking at https://deepstream.io for keeping clients in sync. You will still have to watch the db, though the client and back end sync is handled! - Source: Hacker News / 24 days ago

Https://deepstream.io/ - a popular open source realtime server and https://golden-layout.com/ - the leading layout manager for Web Apps - among many other things. You can find more examples of my work at https://wolframhempel.github.io/me/ My specialties are complex, graphically demanding Web Apps and Cloud server architectures. Over the years I've gotten incredibly good at helping my clients deliver some of the... - Source: Hacker News / 4 months ago

Wolfram previously built https://arcentry.com/, https://deepstream.io/ and https://golden-layout.com/, Adam is Director of Engineering for a trading tech company and. - Source: Hacker News / 11 months ago

OS projects: https://deepstream.io/, https://vramework.io/. - Source: Hacker News / over 1 year ago

Deepstream is an open-source library for real-time web application development. The library, which is built with Node.js and Engine.io, helps developers build frontend web applications that perform real-time updates while requiring minimal backend code. - Source: dev.to / over 1 year 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