I'm developing a system using AngularJS and Websocket (PHP or NodeJS I'm still defining), where the form information I intend to save via socket, ie sending an array with the information and processing it to save to the database and returning the confirmation, and in the same way I want to bring the data via socket.
With all layouts handled via AngularJS the most common is to bring via $http() , however I want to bring them via socket since I want to keep ALL connected clients connected.
I know this is all possible, and I already have some parts up and running, what I really want is to know the risks I'm running with, server issue no problem, everything elastic and self-balance, issue is performance and dynamic Is it worth all that work? At what point can this become a problem?
Adding ... When a user saves some relevant content to a group, this information besides saved needs to be immediately passed on to the other participants in the group. I know that we can make requests from time to time to check for an update and such for ajax, but I believe it will be more dynamic by doing socket.