What will you choose: Repository Pattern or "smart" business objects?
- It depends on the complexity of the project, but in general "smart" business objects is a better choice as it allows for easier management of business logic.
- It depends on the requirements of the project, but in general Repository Pattern is a better choice as it provides separation of concerns between the data access and business logic.
- It depends on the size of the project, but in general "smart" business objects is a better choice as it reduces the number of classes needed.
- It depends on the team's experience, but in general Repository Pattern is a better choice as it provides a common interface for data access.
The choice between Repository Pattern and "smart" business objects depends on the specific requirements of the project, but in general the Repository Pattern provides better separation of concerns and a common interface for data access.
Loading...