|
|
|
|
|
|
by oscarfr
1948 days ago
|
|
|
We are talking roughly 10s of rows of data per user per day stretching back at most a few years. So no huge volumes. Mostly read. I would like data to be persisted across user sessions. And refreshed either periodically, on user login, or on user action. Depending on source. |
|
|
React + MobX provides, I think, a good answer to the problem of "how do i update the user interface to reflect changes to the application state?" on the front end.
Commercially I have seen Java used almost exclusively for web back ends, really because it handles the kind of concurrency that matter for servers well. .NET is about the same but less popular.
It is easy to write small servers in Python and you can do really fun things with async/await (e.g. bridge message queues) but because Python is fundamentally single threaded the concurrency story is worse than Java. With node.JS you could write both your front-end and back-end in the same language, which sounds appealing, but hardly anybody does it.