/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

1 vote175 views1 answer
Create a slider in the inspector C#
C#
0 vote189 views1 answer
C# extension
C#
1 vote176 views1 answer
Developer memes
C#
0 vote164 views1 answer
.net core 3 entity framework constraint code first image field
C#
0 vote171 views2 answers
C# traverseall elements in class property
C#
0 vote173 views1 answer
Windows forms tablelayoutpanel scroll
C#
0 vote160 views1 answer
Automapper c# initialize error
C#
5 votes174 views4 answers
How to concatenate two arrays in c#
C#
1 vote170 views1 answer
Unity list of gameobjects
C#
0 vote165 views1 answer
Base64 to image c#
C#