Enterprise System Architecture Evaluation criteria
1. Throughput, in a simple desktop system, we can consider the time to copy a file and the size of the copy file as a simple throughput concept, in an enterprise system, we take the equivalent time of the transaction, such as a second can be completed 2w transaction.
2. Latency and response, the time taken to return a reply to a single external request, from the start of the request to the time response period during which the reply was received.
3. Concurrency, the number of transactions that can be done concurrently in a unit time
4. Load capacity, we rarely consider the actual number of online users as a reference, in fact, the load should be at the same time the system can respond to how many requests.
5. Load latency sensitivity, as online users increase, the increase in requests at the same time caused by the delay time is longer, can be accepted by the user
6. Resources, test the load capacity of the hardware, the performance of the CPU, bandwidth, disk performance
7. Expand flexibility, the system is easy to carry out horizontal extension, vertical extension and so on. Functions, subsystems are independent of each other, some functional errors do not affect the global service.
8. Fault tolerance, the system to disk, request and so on error whether there are measures to reduce errors
9. Whether the system can be monitored, at the beginning of the system design, should be considered as the system's monitoring, the future performance evaluation of the system will provide an important reference.
At the beginning of the design involves the log monitoring module, relative to the system without monitoring module to increase the monitoring function, convenient and flexible.
10. The independence of the subsystem, like swimming competitions have their own lanes, track and field runs are their own runway, subsystem planning business to measure the independence between subsystems.
Enterprise System Architecture Evaluation criteria