/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 vote118 views1 answer
Even configuration custom errors page is not working asp.net MVC
C#
-1 vote119 views1 answer
C# list object to json
C#
1 vote135 views1 answer
Code jokes
C#
0 vote118 views1 answer
C# find duplicate
C#
0 vote132 views2 answers
Relative path c#
C#
0 vote117 views2 answers
How many days till christmas
C#
1 vote145 views1 answer
Exit application wpf
C#
0 vote120 views1 answer
Embergene
C#
0 vote137 views1 answer
C# set two dimensional array
C#
0 vote157 views1 answer
Make character move upward forever unity 2d
C#Unity