Entity Framework 6 Code First - Is Repository Implementation a Good One?

Question

I am about to implement an Entity Framework 6 design with a repository and unit of work.

There are so many articles around and I\'m not sure what the best advice is:

Answer 1

You should consider "command/query objects" as an alternative, you can find a bunch of interesting articles around this area, but here is a good one:

https://rob.conery.io/2014/03/03/repositories-and-unitofwork-are-not-a-good-idea/

When you need a transaction over multiple DB objects, use one command object per command to avoid the complexity of the UOW pattern.

A query object per query is likely unnecessary for most projects. Instead you might choose to start with a 'FooQueries' object ...by which I mean you can start with a Repository pattern for READS but name it as "Queries" to be explicit that it does not and should not do any inserts/updates.

Later, you might find splitting out individual query objects worthwhile if you want to add things like authorization and logging, you could feed a query object into a pipeline.