That's definetly one of the options. But developing a good websockets solution in the backend comes at a much higher cost from both technical and management points of view. In this article I present the idea of not using/maintaining sockets on the server side ourselves. We want any SaaS to do it for us: pusher js client library opens a websocket connection to Pusher cloud backend.
I am not great at frontend, so I can't be 100% sure if it's true, but I guess, Vuex can be used with Pusher in the same way as with any other socket library: stackoverflow.com/a/44336198
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.
That's definetly one of the options. But developing a good websockets solution in the backend comes at a much higher cost from both technical and management points of view. In this article I present the idea of not using/maintaining sockets on the server side ourselves. We want any SaaS to do it for us: pusher js client library opens a websocket connection to Pusher cloud backend.
I am not great at frontend, so I can't be 100% sure if it's true, but I guess, Vuex can be used with Pusher in the same way as with any other socket library: stackoverflow.com/a/44336198