IUnitOfWork

Rather than Querable IDbSet, we should send back the Entity Specific Repository object.
Sending Queryable IDbSet cause the Persisence Logic or Querying logic leaked into the Controller
or Services.

Application Specific UOW Class & Interfaces Samples

Its name should be IUnitOfWork.cs

namespace CleanArchitecture.Application.Interfaces
{
    public interface IDatabaseService/IUnitOfWork

    {
        IDbSet<Customer> Customers { get; set; }
        IDbSet<Employee> Employees { get; set; }
        IDbSet<Product> Products { get; set; }
        IDbSet<Sale> Sales { get; set; }
        void Save();
    }

}


using GigHub.Core.Dtos;
using GigHub.Core.Repositories;

namespace GigHub.Core
{
    public interface IUnitOfWork
    {
        IGigRepository Gigs { get; }
        IAttendanceRepository Attendances { get; }
        IGenreRepository Genres { get; }
        IFollowingRepository Followings { get; }
        IApplicationUserRepository Users { get; }
        INotificationRepository Notifications { get; }
        IUserNotificationRepository UserNotifications { get; }
        void Complete();
    }
}




Comments

Post a Comment

Popular posts from this blog

IGenricRepository

Image
public interface IRepository<T> { IEnumerable<T> GetAll(); IEnumerable<T> Find(Expression<Func<T, bool >> query); T GetByID( int id); void Add(T item); void Update(T item); void Delete(T item); } public interface IGenericRepository<T> where T : class { IQueryable<T> GetAll(); IQueryable<T> FindBy(Expression<Func<T, bool>> predicate); void Add(T entity); void Delete(T entity); void Edit(T entity); void Save(); }
Read more

Summary of All Data Source Patterns

Simple Active Record (No Repository ) == RDG++ Simple Data Mapper (No Repository) ==  TDG++ Respository Based Active Record = Simple Active Record++ Repository Based Data Mapper = Simple Data Mapper++ Respository (Active Record) = Simple Active Record++ Repository (Data Mapper) = Simple Data Mapper++ When we are using ADO.NET and writing our own DAL, we are not using any ORM. We are dealing ourself with all dirty work of Data Access Writing SQL,Connections, Resultset fetching n mapping, exceptions, messaging, casting, transactions,updating the database schema and domain model ourself ORMs try to abstract these things out and make our life easy Linq like language for quering data. No connection management No Result set dealing and mapping to Domain Model No exception handling No messages to upper layers No Data type casting No Transation Mgmt, it is done by UOW and Change Tracker Database schema and Domain is synched by Code First Migrations Two Types of ...
Read more