Repository patterns is useful or not

Question

1.00/5 (2 votes)

See more:

Is repository pattern is useful with entity framework or not

What I have tried:

searching on google and asking for friend but i am not get any idea

Posted 1-Nov-16 23:59pm

shipalis

Updated 2-Nov-16 3:56am

Add a Solution

Comments

[no name] 2-Nov-16 7:01am

If it helps you solve a problem, then sure it's useful.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

johannesnestler · Accepted Answer · 2016-11-02T03:56:00

Many argue that EF already implements Repository pattern, so there is no point in abstracting the abstraction....
But, I'm glad I created my own abstraction over it. So one could easily change from EF to another OR-mapper - but I think this is a quite unlikely scenario... But what happens all the time is that there is a new version of EF - and not having to change the dependency (to EF) in a lot of projects is a big benefit. Also writing unit-tests for the data-access code is easier (e.g. by injecting an In-Memory-Repository implementation, which doesn't need a database or -connection for Tests.

So in general (mostly if you use generated models) there is no Point in creating your own absraction over EF.
In very big solutions with many projects, dependency mmnagement is crucial (think about creating Setups and so on). So additional abstraction can have it's benefits. (many other solution possible)

I'd say: If you see a real reason to create your own abstratction, do it. If you don't have one now - follow the YAGNI prinicple!!!

Kind regards Johannes

BillW33 · Accepted Answer · 2016-11-02T03:46:00

Solution 1

The Repository pattern hides the details of how the data is stored/retrieved. If that makes your code easier to read and/or understand then it is "useful". Try reading the examples of Repository pattern here [^] and here[^]

Posted 2-Nov-16 3:46am

BillW33