/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 vote141 views1 answer
Wpf scoll to on new item datagrtid
C#
1 vote111 views1 answer
Exit programm c#
C#
0 vote99 views1 answer
Function to accept interger
C#
-1 vote111 views1 answer
C# current thread id
C#
0 vote104 views1 answer
Regex for accepting a file name c#
C#
21 votes105 views4 answers
C# int to string
C#
6 votes108 views2 answers
Sum of two numbers in c#
C#
-1 vote103 views1 answer
Get sites ip in C#
C#
20 votes110 views4 answers
Generate random string C#
C#
0 vote100 views1 answer
If equal statement c#
C#