thanks for sharing, just small question If it uses websockets to update the page, does that mean you’re persisting a connection with every user at all times when they’re using the app? Sounds expensive to scale compared to a SPA + JSON APIs.
If it uses websockets to update the page, does that mean you’re persisting a connection with every user at all times when they’re using the app
That's correct. It's a little expensive, but you'll be able to push down changes from the server the moment the stuff changes as opposed to having the user poll for changes from a JSON API.
The key win here is I can get the read-time updates, without having to write any JavaScript & worry about maintaining state.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
thanks for sharing, just small question If it uses websockets to update the page, does that mean you’re persisting a connection with every user at all times when they’re using the app? Sounds expensive to scale compared to a SPA + JSON APIs.
That's correct. It's a little expensive, but you'll be able to push down changes from the server the moment the stuff changes as opposed to having the user poll for changes from a JSON API.
The key win here is I can get the read-time updates, without having to write any JavaScript & worry about maintaining state.