/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 vote89 views1 answer
C# get property type of list
C#
2 votes94 views1 answer
Randomm number from 2 different ranges
C#
0 vote93 views1 answer
Dotnet DB context register
C#
0 vote99 views1 answer
How to reset disk permission
C#
0 vote90 views1 answer
Unity unfreeze position in script
C#
0 vote93 views1 answer
Get file id from mongodb without objectid using c#
C#
0 vote100 views1 answer
Setting the parent of a transform which resides in a prefab
C#
0 vote91 views1 answer
C# reflection create generic type
C#
3 votes92 views1 answer
Unity how to rotate something to point to something else
C#
1 vote90 views1 answer
Hide datagrid column c#
C#