/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 vote261 views1 answer
.net new template
C#
1 vote252 views1 answer
Debug raycasthit2d unity
C#
0 vote260 views1 answer
How to coppy a portion of an array in c#
C#
5 votes243 views1 answer
Downlaod file and use C#
C#
1 vote247 views1 answer
Group by ef core
C#
5 votes241 views1 answer
C# random float between two numbers
C#
0 vote243 views1 answer
C# restclient timeout
C#
0 vote234 views1 answer
An existing connection was forcibly closed by the remote host. .net core
C#
0 vote282 views1 answer
Unity error creating asset at path
C#Unity
0 vote248 views1 answer
C# accesseurs
C#