[Chatter] system architecture reconstruction tips

This article is used to record the problems encountered when restructuring the system architecture and the solutions currently being processed. XD should be updated from time to time

 

2012/07/03

 

Naming rule Definition
Problem description: naming rules are not standardized and it is difficult to maintain program code.
Solution: use Microsoft naming rules to improve the quality of program code.

 

System Architecture hierarchy
Problem description: the structural hierarchy is unclear, and its responsibilities are scattered everywhere, so it is easy to change the east to the west.
Solution: the architecture is re-engineered in layers, and duties are separated in layers.

 

System Architecture Module
Problem description: The architecture module has unclear responsibilities and is easy to change to the east and west.
Solution: re-design the system module to separate responsibilities.

 

System Architecture Communication
Problem description: The UI logic is closely dependent on WCF, and the entire system must be configured for debugging, which increases the difficulty of debugging.
Solution: Use IOC to cut communication responsibilities, unbind the UI logic from the WCF, and increase the ability to debug segments.

 

System Architecture Database
Problem description: The system is closely dependent on the Entity Framework. You must have relevant knowledge before debugging the system.
Solution: Use repository pattern to cut the database operation, unbind the domain logic from the data storage, and increase the ability to debug segments.

 

Domain knowledge service
Problem description: knowledge in the product field is very powerful, but domain knowledge is scattered across systems, with low reusability.
Solution: extract knowledge from the product field and use the SOA model to provide services.