Reconstruction: improved the design of existing code. Wonderful book reviews.

The basis of large-scale system reconstruction is still the reconstruction method described in this book, but the overall complexity makes restructuring more difficult. Mastering these refactoring techniques is extremely beneficial for restructuring large systems. However, the reconstruction of large systems, especially complicated legacy systems, has higher requirements for developers. In addition, it not only needs to focus on the details of coding, but also gradually presents the beauty of programming through exquisite reconstruction. It also needs to look down on the system architecture, in order to make refactoring easier, decouples layers and modules. The ultimate goal of restructuring a large system is to improve the system architecture for reuse and scalability, and may even reconstruct a general framework from a complex system. For such legacy systems, in addition to the refactoring techniques introduced in this book, we also need to master the effective dependency solution technology. For specific practices, refer to Michael C. feathers: workingeffectively with legacy code.Code. This macro-level reconstruction technology can be considered as restructuring the architecture. Its importance is self-evident. Unfortunately, this book does not cover this content. In general, architecture reconstruction mainly involves Architecture Principles, logical and physical layers, design consistency, functional division rationality, selection of synchronous and asynchronous processing, message communication mechanism, external interface definition, centralization and distribution and many other factors that even affect the macro-architecture.

 

 

This article is excerpted from refactoring: improving the design of existing code (commentary.

Book details: http://blog.csdn.net/broadview2006/article/details/6601099