Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m not sure where I should implement the caching in my repository pattern.
Should I implement it in the service-logic or in the repository?
GUI -> BusinessLogic (Services) -> DataAccess (Repositories)
I would handle it in the repository/data access layer. The reasoning is because it isn’t up to the business layer on where to get the data from, that is the job of the repository. The repository will then decide where to get the data from, the cache (if it’s not too old) or from the live data source based on the circumstances of the data access logic.
It’s a data access concern more than a business logic issue.