Question

In a layered architecture, which specific mechanism prevents a bottom-level data access layer from inadvertently leaking business logic into the presentation layer?

Accepted Answer

The mechanism that prevents a data access layer from leaking business logic into the presentation layer is the implementation of strict layer abstraction and the use of Data Transfer Objects or DTOs. In a layered architecture, each layer operates as a closed boundary that only communicates with the layer directly above or below it. The data access layer is strictly responsible for retrieving and persisting raw data from a database, while the business logic layer is responsible for processing that data according to application rules. A Data Transfer Object is a simple object used solely to carry data between these layers. By forcing the data access layer to return only raw data encapsulated within a DTO and requiring the business layer to apply logic before passing data to the presentation layer, the architecture ensures that the presentation layer never interacts directly with database-specific structures or raw business calculations. This separation of concerns means the presentation layer only receives finalized, view-ready information. If the data access layer attempted to perform a calculation, such as applying a tax rate, it would violate its purpose because that rule belongs in the business logic layer. By strictly enforcing that the business logic layer sits between the data access layer and the presentation layer, the architecture prevents any functional processing from leaking into the interface, ensuring that the presentation layer remains concerned only with how data is displayed to the user.

Home → All Courses → Engineering and Technology Courses → Software Architecture and System Design → Flashcard

In a layered architecture, which specific mechanism prevents a bottom-level data access layer from inadvertently leaking business logic into the presentation layer?