Structure of a large dashboard application
Unanswered
Polish posted this in #help-forum
PolishOP
Hi,
I just want to get some advice on how I should structure a large full-stack application. I basically am writing a frontend for a whole bunch of API's that pulls a lot of data and displays it. I'm conscious my load times will be slow, as it has to pull over several API's etc.
Should I implement some kind of database and pre-fetch data every X minutes and store it in the database?
Also, how do I deal with things like for example I want to pull the total number of events in the past hour, this number might be 1000. But I want to show in a graph the number of events per hour over the past 30 days, i.e. Hour 1 on day 1 = 1000 events, Hour 2 on day 1 = 1100 events etc.
How best to implement this kind of thing? Do I need a DB in the backend storing this?
I just want to get some advice on how I should structure a large full-stack application. I basically am writing a frontend for a whole bunch of API's that pulls a lot of data and displays it. I'm conscious my load times will be slow, as it has to pull over several API's etc.
Should I implement some kind of database and pre-fetch data every X minutes and store it in the database?
Also, how do I deal with things like for example I want to pull the total number of events in the past hour, this number might be 1000. But I want to show in a graph the number of events per hour over the past 30 days, i.e. Hour 1 on day 1 = 1000 events, Hour 2 on day 1 = 1100 events etc.
How best to implement this kind of thing? Do I need a DB in the backend storing this?
4 Replies
PolishOP
Anyone have any steer?
Dunker
As I know there are databases for time series data, just check those and implement into your app
PolishOP
How do you mean?
Dunker
Have you started app, or just thinking