/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 vote132 views1 answer
Dapper execute with list of ids
C#
0 vote130 views1 answer
Button not working unity
C#
7 votes132 views6 answers
C# how to exit program
C#
0 vote283 views2 answers
OpenBots convert String
C#
0 vote131 views1 answer
Make label visible true c#
C#
5 votes118 views1 answer
How to refer parent class unityu
C#Unity
0 vote130 views1 answer
C# datatable current row
C#
0 vote153 views1 answer
Responsive Bootstrap 4 Admin Dashboard icon cdn
C#
0 vote125 views1 answer
Font dialog c# code
C#
0 vote143 views1 answer
Dynamic add event control c#
C#