DAO 模式是否会破坏凝聚力/SRP?
让我们举个例子:
class AccountDAO {
create(){..}
read(){..}
update(){..}
delete() {..}
}
有多少责任? 1 还是 4?
Let's use as example:
class AccountDAO {
create(){..}
read(){..}
update(){..}
delete() {..}
}
How many responsibilities are there? 1 or 4?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
SRP不应该被严格地理解。一个对象应该有很少的职责,而不是“一个”。
这里AccountDAO只负责Account持久化,因此它只有一项职责。
SRP shouldn't be understood in a strict manner. One object should have very few responsibilities, not "one".
Here AccountDAO is only responsible for Account persistence, so it has only one responsibility.