/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

4 votes191 views10 answers
C++
C#
1 vote125 views1 answer
C# find element by condition
C#
1 vote129 views2 answers
Unity for loop array
C#
0 vote122 views1 answer
Unity set terrain to image
C#
0 vote119 views1 answer
Unity OVR Headset
C#
-1 vote133 views1 answer
Getcomponent rigidbody2d
C#
2 votes129 views1 answer
C# how to check if two lists have same values
C#
2 votes154 views1 answer
Join array element in c#
C#
17 votes116 views1 answer
Float c++
C#
0 vote133 views1 answer
Set current date to textbox in asp.net
C#