C# service domain-driven-design repository-pattern

存储库和服务层交互问题

发布于 2024-10-15 05:40:25 字数 702 浏览 1 评论 0原文

我有一个通用存储库接口，它具有从服务层保存、读取和查询的常用方法，如下所示：

public interface IRepository<T>
{
    T GetById(int id);
    void Save(T entity);
    void Update(T entity);
    void Delete(T entity);
    IEnumerable<T> GetAll();
}

如果我有一个服务，例如使用 IRepository 的具体实现的用户服务> 以 User 作为其类型 (IRepository)，如果服务本身可能需要来自另一个 IRepository 的内容，请说 IRepositoryAdmin> 服务应该直接调用 IRepository，还是应该调用关联的服务（即主要处理 IRepository 的服务） > 存储库）？

如果您直接从存储库中提取项目，如果您想在结果返回给客户端之前应用某些业务规则，但另一方面，服务可能希望处理原始结果，我个人会看到一个问题设置并将其自己的规则应用于结果，所以我对采取哪个方向有点困惑，任何建议将不胜感激。

原文

I have a generic repository interface, that has the usual methods for saving, reading and querying from the service tier like so:

public interface IRepository<T>
{
    T GetById(int id);
    void Save(T entity);
    void Update(T entity);
    void Delete(T entity);
    IEnumerable<T> GetAll();
}

If I have a service, for example a User service that uses a concrete implementation of the IRepository with User as its type (IRepository<User>), if the service itself might need something from another IRepository say IRepository<Admin> should the service call IRepository<Admin> directly, or should it call an associated service (i.e., the service that primarily deals with the IRepository<Admin> repository)?

I personally can see an issue if you are pulling items directly from a repository, if say you wanted to apply certain business rules before the results are returned to a client, but on the other-hand a service might want to work on the raw result set and to apply its own rules to the results, so I am a bit confused about which direction to take, any suggestions would be greatly appreciated.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

倾城月光淡如水﹏ 2024-10-22 05:40:25

如果所有存储库的实现细节相同，您可能可以创建一个抽象的 BaseRepository，例如：

protected abstract class BaseRepo<T> : IRepository<T>
     where T : class
{
    #region IRepository Members

    // Implement all IRepository members here and make them public

    #endregion
}

然后您可以创建一个专用的 AdminRepository，例如：

public class AdminRepo : BaseRepo<Admin> {}

并从另一个存储库调用，您可以执行以下操作：

public class UserRepo : BaseRepo<User>
{
    private AdminRepo adminRepo = new AdminRepo();

    public UserRepo()
    {
        Admin person = adminRepo.GetById(1);
    }
}

希望有所帮助。

If the implementation detail of all the repositories is same, you could probably create an abstract BaseRepository, for example:

protected abstract class BaseRepo<T> : IRepository<T>
     where T : class
{
    #region IRepository Members

    // Implement all IRepository members here and make them public

    #endregion
}

then you can create a dedicated AdminRepository, for example:

public class AdminRepo : BaseRepo<Admin> {}

and to call from another repository you can do the following:

public class UserRepo : BaseRepo<User>
{
    private AdminRepo adminRepo = new AdminRepo();

    public UserRepo()
    {
        Admin person = adminRepo.GetById(1);
    }
}

hope that helps.

回复收藏 0 原文

~没有更多了~