/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 vote182 views1 answer
Jaro–winkler distance c#
C#
3 votes165 views3 answers
Convert ienumerable to list
C#
0 vote137 views1 answer
Button commandfield commandargument pass textbox
C#
50 votes151 views3 answers
C# int array
C#
1 vote141 views1 answer
Space custom inspector
C#
0 vote144 views1 answer
O thread de chamada não pode aceder a este objecto porque existe outro thread que já o tem
C#
0 vote135 views2 answers
C# generate random date
C#
0 vote154 views2 answers
__dopostback
C#
0 vote188 views1 answer
Void to action c#
C#
0 vote152 views1 answer
Syoutube
C#