Just to be sure in my undersanding, let’s suppose user “A” modifies some informations in a grid, updates are of course pushed on the server, nothing new here 
Now user “B” on a page containing a grid component displaying the same data source. The grid informations will be updated automatically in near real time (or supposed to) to display modifications of user “A”, right ?
Yep, that is the main idea behind live update.
The update speed only limited to user connection, normally it must be lesser than a second between data change in one grid, and update for all other users.
The feature is a killing one and really great dhtmlx decided to catch it.
Now, on the performance side effect, users have to consider this very carefully as once a website has quite some success, the servers have great chances to dive into a situation where “suffering”’ is just a little word below the reality.
Do you have advice regarding monitoring tools, cluster archictecture for this use case, or whatever useful for this kind of use ?
Do you have advice regarding monitoring tools, cluster archictecture for this use case, or whatever useful for this kind of use ?
Unfortunately no.
But I think it is not a big deal.
Medium dedicated nodejs server can handle 10 000 parallel connections easily, and if correctly tuned - it is up to 100 000 connections.
Thanks you Stanislav.
Did you have a look on Vert.x ? https://vertxproject.wordpress.com/2012/05/09/vert-x-vs-node-js-simple-http-benchmarks/
It’s supposed to be a ot faster than nodejs in addition to be polyglot.
Yes, i know, it’s java on the backend.