The System Architecture mode:
- Unified exception
- Uniform exception handling is the first step in guaranteeing the correctness of a program, which is the first schema pattern. How to achieve this, see the previous article.
- Log
- The log is also a great means of ensuring that the program is correct, although the log is recorded after the error occurs. But the log is a quick confirmation of the problem and analyzes the important means of hiding the problem.
- Key points
- Log files are differentiated by level, separating errors from normal debug logs
- Log file scrolling method, you can scroll by day and by size, scheduled cleanup
- Log level to adjust settings in real time
- Performance
Support System:
- Test system
- Automated unit testing to ensure the correctness of the base module
- Automated functional testing to ensure the correctness of each code update
- Monitoring System
- Monitoring abnormal log, timely alarm
- Operation and Maintenance system
- Automated release to reduce errors caused by human actions
- Batch release, can be online small data volume testing, ensure that the function is correct, and then all upgrade
- Reconciliation System
- For money or inventory related systems, need to have a real-time reconciliation system, check whether each order is in line with the expected, timely stop loss
Architect Express-The correctness of the architectural goals
