A quick view of Data Snapshot

database icon? XD

Before everything, I must thank to all the subscribers to my story. You’re the triggers why I insist on sharing data point of views. Thank you my virtual friends.

Definition

What’s data snapshots? We can consider it as a slice of tree trunk. Every slice of wood is a record of its partial of life. Combination all the slices into one whole unit is the entire life of data.

Use

Why we need data snapshots? It’s quite essential. Actually, every record in anytime in specific use case, we can use it as a data snapshot. For example, “the connection counts of players on our service platform in the past hour. We try to figure out the issue about the service instability.”

Ya. Do NOT ever forget the target why we use the data.

We can cut (calculate) the counts of the connection counts every hour as a report and store into the “data snapshots”.

Management of data snapshots

OK. Here comes the main discussion I want to share and discuss with you. As a data guy, HOW to manage those data snapshots, data or whatever you call them?

It’s really really really interesting and I have to share the idea with another 3 articles. Otherwise, it will be too long to read. The outlines:

1. Architecture design
   - storage
   - layers
2. Data design
   - schema
   - index
3. Report/ Analysis design
   - Report
   - Analysis

Storage