/C#/Difference between UnitOfWork and Repository Pattern

Difference between UnitOfWork and Repository Pattern

Repository can work without Unit Of Work, so it can also have Save method.

public interface IRepository<T>
{
     T Get(int id);
     void Add(T entity);
     void Update(T entity);
     void Remove(T entity);
     void Save();
}
Unit Of Work is used when you have multiple repositories (may have different data context). It keeps track of all changes in a transaction until you call Commit method to persist all changes to database(file in this case).

So, when you call Add/Update/Remove in the Repository, it only changes the status of the entity, mark it as Added, Removed or Dirty... When you call Commit, Unit Of Work will loop through repositories and perform actual persistence:

If repositories share the same data context, the Unit Of Work can work directly with the data context for higher performance(open and write file in this case).

If repositories have different data context(different databases or files), the Unit Of Work will call each repository's Save method in a same TransactionScope.

Source: stackoverflow.com

Similar codes

0 vote320 views1 answer
Windows forms tablelayoutpanel scroll
C#
2 votes347 views1 answer
Linq query select top 1 c#
C#
3 votes248 views1 answer
Unity player look at mouse
C#
0 vote319 views1 answer
Install Mono project on Ubuntu 20.04
C#
0 vote350 views1 answer
C# max in 2d array row
C#
0 vote318 views1 answer
ActionExecutingContext result response return objects
C#
0 vote275 views1 answer
Vb.net convert int32 into boolean array stack overflow
C#
3 votes341 views1 answer
C# merging two arrays
C#
0 vote324 views1 answer
Csharp-for-loop
C#
0 vote355 views1 answer
Conveyor function in f#
C#