core

An excellent decision, I guess. I'm somehow thinking way too much about such details instead of starting any project. In my previous job, we have used PHP at the backend, but somehow, I like the syntax of python much more. And the community and number of projects around Django are just mind-boggling. So you are probably using Django-REST for the API? With react-virtualized, you are already on the right path as virtual rendering - rendering only the currently visible cells - is the key in regards to the performance of DOM-based approaches. But if you want to reach google sheets performance, there is probably no way around canvas-based rendering (e.g. https://github.com/fin-hypergrid/core or https://github.com/TonyGermaneri/canvas-datagrid). Office 365 seems to use a canvas-based approach as well. The problem with the canvas-based approach

For updating grids, you can achieve very fast performance using batched transactions: https://medium.com/ag-grid/how-to-test-for-the-best-html5-gr... If that's not fast enough, there are canvas based grid which can improve the refresh rates faster. Hypergrid is a canvas based grid, though it's not the easiest to work with: https://github.com/fin-hypergrid/core JPMorgan has release Perspective, which demonstrates streaming updates using WebAssembly: https://perspective.finos.org/ Really comes down to your specific situation what approach is best.