| Languages >> .net |
Implementing the Repository Pattern
| Language: | English | Quality: | Average | Has Audio: | true | Source: | Google Videos | Media: | Flash | Posted On: | 03 Feb 09 |
|
Mike Hadlow starts his talk by summarising the evolution of data access from the early days of using RDO and DAO with Visual Basic, which did not provide a lot of control over the database, to contemporary domain driven approaches. He goes on explaining the different meanings people tend to give to the term “Repository”. He explains that, the Repository pattern is important for providing dependency-free access to data of any type. Repositories are responsible for persisting entities and value types. The core purpose of the repository is to encapsulate persistence. “The client should appear to be simply using an entity collection and all the details of object relational mapping and specific data access APIs should be hidden behind that collection like interface”. Mike goes on with his thoughts on some questions like: Should we return IQuaryable objects from our repositories? Should repositories control transactions and who should consume the repositories? |
Tags: SkillMatter, .net, Pattern, RDO, DAO, Design, Development, [SUGGEST A TAG]
|
Other dowloadable format of this video
|
Video in Power point presentation format
Resolution : |
|
