L2S（LINQ to SQL）或EF（实体框架） [英] L2S (LINQ to SQL) or EF (Entity Framework)
问题描述
我将重建现有的中等规模的网络应用程序，用于供应链管理网络解决方案。核心将围绕一些Item\Site组合记录，Organization \User管理，显示组织特定数据（具有2个级别的网格的仪表板）和Drilldown，其具有用于项目事务的一些复杂计算以及用于显示的鲁棒网格
I'm going to rebuilt an existing moderate-scale web-app to be used for a supply-chain-management web-solution. The core would be around some Item\Site combination-records, Organization\User management, display Organization specific data (a dashboard with 2 levels of Grid) and a Drilldown which has some complex calculations for Item transactions and a robust Grid to show multiple level of totals, sub-totals, etc...
过去，我使用
开发了ASP.Net 2.0和ADO.Net，后端
是SQL-Server。我认为迁移
这个web解决方案到一个完整的基础
基于ASP.Net v3.5的MVC架构
和集成其他部分如
Membership API，验证框架，
等...它将是一个完整的
重新设计。性能和
可扩展性（即处理百万
记录，执行快速计算，
快速响应时间等）是
两个主要优先级。另外
简单和长期维护
和任何级别的定期升级是
也要考虑。
In past, I had developed it using ASP.Net 2.0 and ADO.Net, the backend is SQL-Server. I'm suppose to migrate this web-solution to a full fiedge ASP.Net v3.5 based MVC architecture and integrate other pieces like Membership API, Validation-framework, etc... its going to be a complete re-design. The performance and scalability (i.e. handle millions of records, perform quick calculations, quick-response-time, etc..) are the two main priorities. In addition simplicity and long-term maintenance and periodic upgrades at any level are also to be considered.
我想知道下面哪两个会使一个健壮的DAL满足我的上述要求：
I was wondering which of the following two would make a robust DAL which meets my above mentioned requirements:
- L2S到SQL）或EF（Entity
Framework）
我一直在搜索很多，喜欢验证我的理解：
I've been searching a lot and based on that I'd like to verify my understanding:
- L2S像Win98-强大，稳定，简单， / li>
- 是EF类似WinXP - 更好的win98，也稳定在一种方式，但
更多的层，所以可能有一个
差异性能和简单性
与L2S相比
我不认为我们将涉及'在我们的开发中，SQL-Server会留下来。另外，我不认为我们需要实际映射多个表到一个实体等。通常，我们将有一个到我们的数据库表到实体（即用户，组织等）的映射。 。）和一些复杂的情况 - 例如仪表板从多个表中获取记录（很可能我们需要使用存储过程和/或DB VIEW）。
Drilldown页面从单个表中提取数据，但是有很多计算，所以我们再次计划使用一个存储过程，这将为我们提供一个格式化的表（但是这个表可能不像DB中已经存在的那样） ）
I don't think we're going to involve 'multiple-databases' in our development, SQL-Server will stay. Also, I don't think we'll need to actually map multiple-tables to an Entity, etc... Generally, we'll have one to one mapping for our DB-tables to Entities (i.e. User, Org, etc..) and for some complex cases - like the dashboard fetches records from multiple tables (most probably we'll need to use a stored-procedure and/or a DB VIEW). The Drilldown page fetches data from a single table but has many calculations so again we're planning to usa a stored-procedure which will provide us a formatted table (but this table might not look like the ones already present in DB)
所以，这是一些棘手的映射，但除了我们需要保持简单，考虑性能和可扩展性。哦!
简单，快速，简单，快速。 ，可扩展&
Simple, fast, scalable & performing - thats what we need!
预先感谢 - 请指导我。
Thanks in advance - please guide me.
短 - ADO.NET实体框架何时使用它vs Linq到SQL
详细信息 - 在ADO.NET实体框架和LINQ to SQL之间进行选择
列表 - 在LINQ到SQL和实体框架之间选择
List - Choosing between LINQ to SQL and Entity Framework
推荐答案
我喜欢L2Sql作为Win98的比较，但我会比较EF到Vista ...它有很大的潜力，但比特留下，直到他们出来与下一个版本，使它像一个死亡的一千个。
I like the comparrison of L2Sql as Win98, but I would compare the EF to Vista ... it's got lots of power potentially but bits left undone until they came out with the next version make it like a death of a thousand cuts.
我正在寻找EF 4 ...我希望它是Windows 7保持你的比喻。
I am looking foward to the EF 4 ... I am hoping it is Windows 7 to stay with your analogy.
这篇关于L2S（LINQ to SQL）或EF（实体框架）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
