/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

2 votes201 views2 answers
C# regex number only
C#
0 vote168 views1 answer
Drop down list razor example
C#
0 vote167 views1 answer
C# ensure static constructor is called
C#
0 vote169 views1 answer
How to make text show a variable in unity
C#
0 vote139 views1 answer
Radiobutton in asp.net
C#
0 vote171 views1 answer
C# open access database mdb
C#
0 vote148 views1 answer
Window height in C# forms
C#
0 vote154 views1 answer
AutoFixture ignore property
C#
0 vote170 views1 answer
Singleton pattern c# stack overflow
C#
0 vote171 views1 answer
Button pervious for picturebox c#
C#