QOS (Duration Statistics)
Class structure
Record manager
Recorder
- Page type (through the HOOK of the interface life cycle)
- Streaming (news)
- Custom (horizontal sliding "video playback")
Scene [a sports event]
Different types of loggers?
- Starting point: different business scenarios, different packages. Reflects good scalability
How to reduce the data loss rate? [The program is killed or shut down by power off]
- Write to disk regularly
- Limit the number of items in the memory cache [for example: read and write if more than 20 items]
The specific scene of delayed upload?
- Front and back switch
- Network changes
- Lightweight interface piggybacking [Business coupling] Not recommended
important point
The structure is somewhat similar to the command mode
- Recorders can be specific to different business classes
XMind - Trial Version