The repository pattern is an abstraction.
Objects can be added to and removed from the Repository, as they can from a simple collection of objects, and the mapping code encapsulated by the Repository will carry out the appropriate operations behind the scenes. Client objects construct query specifications declaratively and submit them to Repository for satisfaction. This post (which is the third in a series about the data layer) aims to explain why it’s still a great choice.Ī Repository mediates between the domain and data mapping layers, acting like an in-memory domain object collection. Especially about its usefulness since the introduction of OR/M libraries. The repository pattern has been discussed a lot lately.
