In this Isaac Abraham adds that repository doesn’t make testing any easier, which is one thing it was supposed to do. What Rob calls ‘this over-abstraction silliness’.Īnother blog is ‘ Why Entity Framework renders the Repository pattern obsolete’. Rob Conery’s main point is that the repository & UnitOfWork just duplicates what Entity Framework (EF) DbContext give you anyway, so why hide a perfectly good framework behind a façade that adds no value. The most cogent and well thought-out post of this kind is ‘ Repositories On Top UnitOfWork Are Not a Good Idea’. In researching as part of my review of the current Spatial Modeller™ design I found some blog posts that make a compelling case for ditching the repository. What people are saying against the repository pattern However we don’t learn unless we hear from others that have a counter view, so let me try and summarise the arguments I have seen against the repository/Unit of Work pattern. In Spatial Modeller™ I think I have perfected the design and use of these patterns and I am quite pleased with how it helps the overall design. I have use the repository pattern and UnitOfWork pattern over many years, even back in the ADO.NET days. Software design of Spatial Modeller Web app The design of Spatial Modeller™ is a fairly standard four layer architecture. I am now undertaking a critical review of its design and implementation to see what I could improve in V2. I have just finished the first release of Spatial Modeller™, a medium sized ASP.NET MVC web application.
#Ef select to new dto with icollections update
UPDATE (2018): Big re-write to take into account Entity Framework Core, and further learning.Part 2: Four months on – my solution to replacing the Repository pattern.Part 1: Analysing whether Repository pattern useful with Entity Framework ( this article).
0 kommentar(er)
