Three-tier architecture
Architecture patterns:
Architectural pattern is a software system refers to the overall organizational structure
Some rules and guidelines describe the software system architecture model of organizational structure
These rules and guidelines, we can pre-defined, clear responsibilities subsystems efficiently organized
Design Patterns:
Design pattern is described in a local software systems continue to reproduce the core solution
These solutions are designed to improve the structure appear, can be applied to similar circumstances in the future appears.
And architectural patterns compared to the design pattern is concerned that more micro issues.
Three-tier architecture model belongs mode, the entire business application from low to high is divided into: presentation layer, business logic, data access layer (persistence layer).
Presentation layer: complete impression data, and provides an interface for the user to input data
Yewuluojiceng: memory data service processing operation is completed
Data Access Layer: completion of data between the memory and database intercross
Persistence DAO mode, the data (Data Access Object)
Establishing entity classes and mapping database table, which is table which corresponds to the class, which column (ORM) which corresponds to the attribute.
Objective data persistence layer is to complete the conversion object data and relational data.
Business logic layer using things script mode
Script: The operation of a business, all packaged as a method of
To ensure that a business approach, all database update operations while successfully, or both fail. Does not allow partial success, partial failure, thus causing confusion data operation (transaction)
It represents the MVC pattern layer
M: model entity class is responsible for data encapsulation and data transmission
V:. View is a form GUI and GUI components, responsible for providing an interface for data exchange and data, and data presentation
C: Control is responsible for event processing control of business processes.
Business Interface design principles: a physical interface to a class once submitted a business methods of argument from the presentation layer
Persistent interface design principles: a persistent entity class interface to a persistent database operation method of a
Interface segregation principle: the use of specialized interface is better than with a unified interface, then the organization and division of the project, do not let the developer less than face their own way.
