blocks|key|317230|text|首先，实体框架实现了一个仓库模式和一个工作单元模式。在类似于实体框架的现代ORM之上实现存储库和工作模式单元是一个额外的抽象层，它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|317231|缩小了潜在ORM的可能性|unordered-list-item|317232|不为基础ORM提供额外的价值。|317233|充其量一文不值，但可能是有害的|317234|这种实现的目的之一是将查询逻辑封装在存储库中，而不是像单一责任原则(SRP)这样的查询，而是几个查询，从而违反了查询逻辑。您可以做的是依赖于ORM，并将广泛的查询逻辑封装在单个查询类中。|offset|length|317235|我的建议不是通过在抽象层上添加抽象层来满足“最佳实践”，而是尝试使用一些更通用的设计准则(如实心+)来解决问题。|317236|Ayende在一系列博客文章(这里、这里、这里、这里、这里、这里、这里和这里)中回顾了Northwind应用程序，这些文章涉及应用程序中所谓的最佳实践。这是一个伟大的阅读！|317237|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Single_responsibility_principle|1|http://en.wikipedia.org/wiki/SOLID_%2528object-oriented_design%2529|2|http://ayende.com/blog/153059/northwind-starter-kit-review-if-you-wonrsquo-t-respect-the-database-there-will-be-pain|3|http://ayende.com/blog/153699/ask-ayende-repository-for-abstracting-multiple-data-sources|4|http://ayende.com/blog/153153/northwind-starter-kit-review-refactoring-to-an-actual-read-model|5|http://ayende.com/blog/153058/northwind-starter-kit-review-data-access-review-thoughts|6|http://ayende.com/blog/153057/northwind-starter-kit-review-the-parents-have-eaten-sour-grapes-and-the-childrenrsquo-s-teeth-are-set-on-edge|7|http://ayende.com/blog/153029/northwind-starter-kit-review-data-access-and-the-essence-of-needless-work-part-ii|8|http://ayende.com/blog/153028/northwind-starter-kit-review-data-access-and-the-essence-of-needless-work-part-i|9|http://ayende.com/blog/152706/application-review-northwind-starter-kit^0|0|0|0|0|Y|3|0|0|1A|2|1|0|F|2|2|I|2|3|L|2|4|O|2|5|R|2|6|U|2|7|X|2|8|10|2|9|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1H|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|1I|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|1J|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1K|8|@]|9|@$K|1L|L|1M|1|1N]]|A|$]]|$1|M|3|N|5|6|7|1O|8|@]|9|@$K|1P|L|1Q|1|1R]]|A|$]]|$1|O|3|P|5|6|7|1S|8|@]|9|@$K|1T|L|1U|1|1V]|$K|1W|L|1X|1|1Y]|$K|1Z|L|20|1|21]|$K|22|L|23|1|24]|$K|25|L|26|1|27]|$K|28|L|29|1|2A]|$K|2B|L|2C|1|2D]|$K|2E|L|2F|1|2G]]|A|$]]|$1|Q|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]|10|$5|T|U|V|A|$W|11]]|12|$5|T|U|V|A|$W|13]]|14|$5|T|U|V|A|$W|15]]|16|$5|T|U|V|A|$W|17]]|18|$5|T|U|V|A|$W|19]]|1A|$5|T|U|V|A|$W|1B]]|1C|$5|T|U|V|A|$W|1D]]|1E|$5|T|U|V|A|$W|1F]]]]

First to say Entity Framework implements a Repository pattern and a Unit of Work Pattern. Implementing Repository and Unit of Work patterns on top of a modern ORM like Entity framework is an additional layer of abstraction that:

<ul>
<li>narrows the possibilities of the underlying ORM </li>
<li>does not provide additional value to the underlying ORM</li>
<li>is at best worthless but may be harmful </li>
</ul>

One purpose of such implementations is to encapsulate the query logic in the Repository and not one query like Single Responsibility Principle (<a href="http://en.wikipedia.org/wiki/Single_responsibility_principle" rel="nofollow">SRP</a>) would suggest, but a couple of queries and thus violating SRP. What you could do is to rely on your ORM and encapsulate extensive query logic in single Query classes.

My suggestion is not to please "best practices" by adding abstraction layers on abstraction layers and so on but to try to solve a problem using some more general design guidelines such as <a href="http://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29" rel="nofollow">SOLID</a>.

Ayende Rahien reviews the Northwind Starter Kit application in a series of blog posts (<a href="http://ayende.com/blog/153059/northwind-starter-kit-review-if-you-wonrsquo-t-respect-the-database-there-will-be-pain" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153699/ask-ayende-repository-for-abstracting-multiple-data-sources" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153153/northwind-starter-kit-review-refactoring-to-an-actual-read-model" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153058/northwind-starter-kit-review-data-access-review-thoughts" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153057/northwind-starter-kit-review-the-parents-have-eaten-sour-grapes-and-the-childrenrsquo-s-teeth-are-set-on-edge" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153029/northwind-starter-kit-review-data-access-and-the-essence-of-needless-work-part-ii" rel="nofollow">here</a>, <a href="http://ayende.com/blog/153028/northwind-starter-kit-review-data-access-and-the-essence-of-needless-work-part-i" rel="nofollow">here</a> and <a href="http://ayende.com/blog/152706/application-review-northwind-starter-kit" rel="nofollow">here</a>) in <a href="http://ayende.com/blog" rel="nofollow">his blog</a> that deal with so called best practices applied in an application. This is a great read!

I have spent a lot of time searching for best practices for designing a ASP.NET MVC 3 web site using EF 4.1 or another ORM. I found this <a href="http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application" rel="nofollow">tutorial on Implementing the Repository and Unit of Work Patterns in an ASP.NET MVC Application</a> . It was a good tutorial and I learned something. So this got me thinking and wanted to know from the people on stack is this something you would use? if not why and how did you design your web site? I just want to learn the correct way to do things and understand why one way is better then the other.

ASP.NET MVC 3 best practice / design

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我花了很多时间寻找使用EF4.1或其他ORM设计ASP.NET MVC 3网站的最佳实践。我找到了这个。这是一个很好的教程，我学到了一些东西。所以这让我思考，想从堆里的人那里知道这是你会用的东西吗？如果不是，为什么以及你是如何设计你的网站的？我只想学习正确的做事方法，明白为什么一种方法比另一种更好。

问ASP.NET MVC 3最佳实践/设计
EN

回答 1

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC 3最佳实践/设计EN