什么是可扩展性最佳的数据访问范例？ [英] What is the best data access paradigm for scalability?

问题描述

有这么多不同的选择走出微软的数据访问。哪一个是最好的可扩展的应用程序？

There are so many different options coming out of microsoft for data access. Which one is the best for scalable apps?

的LINQ

我们应该使用LINQ？这当然似乎很容易，但如果你知道你的SQL是否真的帮助。此外，我听说你不能在ASP.NET中使用LINQ运行异步查询。因此，我不知道它是否真的是可扩展性？是否有使用LINQ任何真正的大网站（用计算器可能是个例外）。

Should we be using Linq? It certainly seems easy but if you know your SQL does it really help. Also I hear that you can't run Async queries in ASP.NET using Linq. Therefore I wonder if it is really scalable? Are there any really big sites using Linq (With the possible exception of stackoverflow).

实体框架

不要听到实体框架这么多华丽堂皇。似乎更接近对象模型我与familure。

Don't hear so much razzmatazz about the Entity Framework. Seems closer to the Object model I'm familure with.

道夫/动态数据

我们是否应该公开我们的数据作为一种服务？

Should we be exposing our data as a service?

我是pretty的困惑和多数民众赞成在我进入了其他的ORM产品，如NHibernate的。任何意见或智慧哪个好？

I'm pretty confused and thats before I get into the other ORM products like NHibernate. Any ideas or wisdom on which is better?

推荐答案

我会建议无论是NHibernate的或实体框架。对于大型网站，我会使用ADO.NET数据服务。我不会做任何事情与大LINQ to SQL的。我认为堆栈溢出可能最终得到了一些有趣的问题，规模为2层，而不是3层，他们也将有一定的麻烦重构作为数据库变化的物理方面和这些变化波及整个code。只是一个想法。

I would recommend either NHibernate or Entity Framework. For large sites, I'd use ADO.NET Data Services. I wouldn't do anything large with LINQ to SQL. I think Stack Overflow might end up with some interesting scale problems being 2-tier rather than 3-tier, and they'll also have some trouble refactoring as the physical aspects of the database change and those changes ripple throughout the code. Just a thought.

这篇关于什么是可扩展性最佳的数据访问范例？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！