【正文】
and change the design for the top of the bottom in terms of their call has no effect. If the stratified design, interface design to follow for the idea, then this dependence should be down is a weak dependence. Without changing the interface and thus the premise of the definition of an ideal layered structure should be a support can be taken to replace the drawer style architecture. For this reason, the Business Logic Tier design for a scalable architecture to support is particularly crucial, since it plays two different roles. It is the caller for the data access layer, it is by the caller for that layer is concerned. Dependence and the relationship was dependent on entangled in the Business Logic Tier, the dependence of how to achieve the decoupling, it is outside the business logic in addition to the achievement of the task left to the designer. Data Access Layer(DAL): Data Access Layer: Sometimes also known as the persistence layer, its function is responsible for database access, you can access the database system, binary files, text documents or XML to realize that a simple table of data Select, Insert, Update, Delete operations. If you want to join the elements of ORM, it will include between objects and data tables of the mapping, as well as the object of persistent entities.