/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 vote104 views1 answer
Prometheus add prefix to metrics
C#
0 vote133 views1 answer
C# Arithmetic operators
C#
0 vote154 views1 answer
Unpacking c # tuple
C#
0 vote142 views2 answers
Wpf resource dictionary
C#
2 votes138 views2 answers
Missingpluginexception (missingpluginexception(no implementation found for method firebase#initializecore on channel plugins.flutter.io/firebase_core)
C#
1 vote164 views1 answer
C# unity control key input
C#Unity
1 vote140 views1 answer
Initialize ConsoleLoggerProvider in EF core
C#
0 vote151 views1 answer
C# HttpResponseMessage postResponse = client.PostAsync
C#
46 votes131 views6 answers
Unity C# random number
C#
0 vote137 views1 answer
Dotnet.com
C#