Yesterday afternoon and Shen discussed the problem of a website, I proposed a question: When I organize the object of the BusinessFacade layer, I found that the inquiry, insert, and updated operations of the same area object is separate. Is it in a few classes, is it to consider merged them into an object of a businessfacade layer?
He gave me a very inspiration: BusinessFacade is the logic of packaging business (the caller of the performance layer is called the business appearance layer), then the business logic is not a function such as Crudation (the basic function of the DataAccess layer) However, it is necessary to perform related operations before the crudation, for example, when querying information of a component, while logging this component is viewed once, and recently browsing records, these operations may design a few Different domain objects, but packaged through a unified business appearance layer.
When I discussed the past shopping cart design, I proposed that the shopping cart system designed the unity of the original DUWAMISH architecture, the original architecture adopted the layered style of façade to DataAccess, although the shopping cart system is relatively independent. It can be separated from the physical placement of the project, but it should not be subordinate in different namespaces, because the system itself lacks architectural documentation, so this division is even more chaotic in system logic.
