Relationship between technical solution selection and routine System Maintenance

With the development of software technology, there are more and more methods and technologies to solve the same problem. In projects, developers tend to prefer relatively novel technologies with high development efficiency and fast operation speed. However, it is easy to ignore the impact of technology selection on system maintenance during use.

Here is an example of my experience. Two years ago, a system needed to transmit large data files over the Internet. My colleagues use the background webpage to upload and download data files over HTTP. In system use, I found that the data transmission speed was difficult to meet user requirements. I accepted the improvement work of the system data transmission speed. At that time, the available transmission protocols include HTTP and FTP. After a simple experiment, it is proved that FTP is indeed much faster than HTTP in file transmission, especially when there is a ready-made FTP example.CodeFor reference, it is decided to use ftp to solve the speed problem of data file transmission. The new data transmission system will soon be developed. During system use, it is found that the configuration of the FTP server is complicated, such as FTP service installation, FTP directory ing, and system permission settings for the corresponding file directory, TCP port restrictions and firewall configurations. The client also has port restrictions and access permissions. Fortunately, there was an excellent system administrator in the past two years who was able to promptly discover configuration problems and solve them in a timely manner. There were no major faults in system usage. However, from the end of last year, with the departure of the excellent system administrator and the upgrade of system hardware and operating systems, many configuration-related faults emerged. In particular, as the network security level increases, many applications often only allow port 80 to open, which will make our system completely unavailable.

After this incident, we should not only consider the feasibility of the technology, but also the maintainability of the technology.

For the maintainability of the technology, the client can not be installed (such as using a browser) or press enter through a typical installation path under the strictest restrictions, the system client can be used normally. For the server side, installProgramThe configuration of this technical requirement can be easily implemented without having to interact with the Administrator too much.