Member-only story
(Database) How to store and calculate historical big data with lower usage frequency
The usage frequency of historical data often decreases over time, and how to store and calculate it becomes a problem.
Disclaimer: Your support matters! I have taken on a project to promote open source project. If you find value in the project, a simple fork and star would go a long way in helping me secure this opportunity for the long term. Your contribution means a lot. Thank you!
Low frequency of use does not mean that it is no longer used at all. If all these data are archived from the database, they must be imported into the database again when querying statistics, it is time-consuming and labor-intensive. There is often an awkward situation where the query takes only 3 minutes but the import takes 3 hours.
