title: Is there a reason for using the Repository pattern with Entity Framework if I know I will only ever use EF?
body: <p>From reading various books and articles, I seem to rather often find the usage of the Repository-pattern suggested. I get the point if you need to be able to swap out your data layer from one to another, but my question is, if I know with 100% certainty that I will <em>not</em> use any other tech for data access, is there any reason for using said pattern?</p>
  
  <p>The thing that I find myself doubting the most is that I don't really see what this extra layer of abstraction can bring to the table in this scenario. From my experience, EF with its fluent linq-to-entities -functionality should be more than enough for pretty much all my needs.</p>
  
  <p>The most usual cases seem to start the repositories with methods such as FindAll, Find, Add and Delete, all of which are very easily accessible directly through EF (so no code duplication to speak of).</p>
  
  <p>So am I just missing some big point, or is the repository more for when you need to support multiple different data access technologies?</p>