Timeline for Build an API for a graph app with + 30 millions data points
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2023 at 7:27 | comment | added | Luc Franken | In addition as this is already a great answer: The data returned can be calculated on the spot but can also be pre-calculated in your backend and just stored in the database. That makes your logic for getting the results easier and more performant if you run into that point. Just simple cache tables like: humidity_per_month, humidity_per_week etc. As the data is old it is likely stale and could maybe be calculated once and shown many times. Interesting to read a bit more about data warehouses as well, likely too far for now but the concepts are interesting. | |
| Sep 15, 2023 at 9:36 | comment | added | intern_2004_uk | That's perfect, this is a great solution! thanks | |
| Sep 15, 2023 at 9:34 | vote | accept | intern_2004_uk | ||
| Sep 14, 2023 at 20:00 | history | answered | JimmyJames | CC BY-SA 4.0 |