存储库类中要放入多少内容？
使用存储库模式时，是否建议为每个数据库表使用一个存储库类？我是否也可以将一个服务层类映射到一个存储库类。我很难理解一个存储库或服务层类应该有多少东西。
谢谢！
When using the repository pattern is it recommended to have one Repository class for each database table? Would I also map one service layer class to one repository class. I'm having a hard time trying to understand how much stuff one repository or service layer class should have.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您应该为每个类拥有一个存储库，该存储库是您域中的根聚合。
You should have a single repository for each class that is a root aggregate in your domain.
存储库应该独立于您的数据库结构。它们封装了从数据库到域模型的映射的所有工作，反之亦然。这可能与 1 个数据库表相关，也可能来自 10 个表，这并不重要。
一般来说，一个存储库对应一个域模型类，但这也不是一个牢不可破的规则。如果您有多个密切相关的域类，尤其是在继承或包含关系中，那么存储库处理多个不同类型的情况并不罕见。不过，如果可以的话，尝试只坚持其中一个也是个好主意。
Repositories are supposed to be independent of your database structure. They encapsulate all the work of mapping from the database to your domain model and vice versa. That might relate to 1 database table, or it might come from 10 tables, it doesn't matter.
Generally, a single repository corresponds to a single domain model class, but that's not an unbreakable rule either. If you have several domain classes that are very closely-related, especially in an inheritance or containment relationship, then it's not unusual for a repository to deal with more than one distinct type. Still, it's a good idea to try to stick to just one, if you can.