title: The use of Repository and unit of work patterns (revisited) ... in EF Core with ASP.NET Core
body: <p>I was following <a href="https://docs.microsoft.com/en-us/aspnet/core/data/ef-mvc/advanced#repository-and-unit-of-work-patterns" rel="noreferrer">this tutorial</a> for EF Core with ASP.NET Core. The interesting thing is that this article states that 'the use of Repository and unit of work patterns is not always the best choice for applications that use EF', but in the tutorial of EF 5 the use of repository and unit of work patterns still is promoted even with a seperate tutorial part. </p>
  
  <p>Reading  <a href="https://stackoverflow.com/questions/8749153/why-use-repository-pattern-or-please-explain-it-to-me">old articles</a> on stackoverflow it is reported that the reasons one would apply it is mainly for testing (dependency injection). </p>
  
  <p>Reading further in the turial it is mentioned that 'The Entity Framework Core implements an in-memory database provider that can be used for testing'. I presume this is a new feature that was not there at the time of EF5. Does this mean that there is hardly any reason anymore to apply the use of repository and unit of work patterns in EF Core with ASP.NET Core?</p>