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.
It seems to me that the only difference is that Active Record has CRUD methods in data container class, and the Repository pattern uses separate class for data container and CRUD methods, but surely I’m wrong.
What are the differences between Active Record and Repository pattern? When should I use which pattern?
Essentially, your assumption is correct. The repository and DAO patterns externalize persistance concerns while Active Record internalizes them. I’ve actually seen some implementations where active record classes were injected with a repository instance that provided their persistence concerns internally.
The biggest reason against using the Active Record pattern is simple, your domain objects shouldn’t care how (or even if) they are persisted. The repository pattern provides persistence ignorance to your domain objects by externalizing persistence concerns and providing it as an external service.