Using Repository Pattern With Entity Framework 6

Question

Is it a best practice to implement repository pattern with entity framework 6 (and upper versions)? why? It seems that Microsoft doesn't recommend it!

Answer 1

I think it is a good idea to add repository pattern over entity-framework as it can help you alot in many areas. But it can also add a new layer of complexity. So points to consider are:

• Using repository you can limit clients to specific operations. (Can be a pro or con depending on requirements and implementation)
• You can also provide ready made functions for complex operations so client don't have to repeats that logic.
• Repositories can be made thread safe as DbContext isn't.
• Repositories will allow you to be independent of entity framework so in future if you ever need to move away from it you can just changed underlying functionality easily.
• You can intercept incoming db operations in repository and do whatever you like with them. e.g. add addition where clause in multi-company scenario.
• Testing becomes more easier as it becomes easy to mock underlying functionality.

But Repositories also have others cons. Look at these Is the Repository pattern useful with Entity Framework? and Benefit of Unit of Work and Repository Pattern with Entity Framework