/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 vote338 views2 answers
How to make a game
C#
0 vote355 views1 answer
Ef core unique index
C#
31 votes385 views3 answers
Get key unity
C#Unity
0 vote389 views1 answer
Uninitialized array c#
C#
1 vote344 views1 answer
Unity projectile spread
C#
32 votes417 views4 answers
How to get keyboard input in unity
C#Unity
1 vote353 views1 answer
C# .net core convert int to enum
C#
7 votes313 views5 answers
C# list object
C#
0 vote386 views1 answer
Gridview column cell alignment form c#
C#
89 votes406 views3 answers
How to generate random numbers in c#
C#