Chapter 3 Web Representation Mode
No design strategy is suitable for all situations. This is because software design has the following competitive requirements: eliminating excessive redundancy and excessive complexity.
Model-View-Controller is an underlying design pattern for separating user interface logic and business logic.
If you copy public logic within a different view of the system, you need to concentrate this logic to reduce the code weight. Deleting a duplicate code is the key to the overall maintenanceability of the system. The data retrieval is preferably also concentrated in one position. A good example is let a series of views use the same data in the database. Retrieving search of this data is better in one location compared to each view to retrieve data and repeat the database access code. Testing the user interface code is often time consuming. Overall tonability can be improved by distinguishing between individual characters. This is not only suitable for model code, but also for controller code.
Chapter 4 Deployment Mode
When building a corporate class solution, not only involve development custom software, but also involves deploying the software into the production server environment. This is the intersection of software development work and system infrastructure.
Unless the company's culture is considered to be equally important, the communication between the application development team and the system infrastructure team will not produce the optimal deployment plan. The two teams must be flexible and willing to reach compromise to make both parties to achieve their requirements.
