如何可扩展性是数据集？团队成员要使用的数据集进行数据检索和操作，使用内置数据完整性等使用对象来进行数据更新等。

How scalable are datasets? Team member wants to use datasets for data retrieval and manipulation, use the built in data integrity etc. to use the object to perform data updates etc.

我们的系统预计将扩展到数百万用户。

Our system is expected to scale to millions of users.

这是我所读到的一切是对数据集的在企业环境中，我错了这里还是什么？

Everything that I have read is against dataset's in an enterprise environment, am I wrong here or what?

推荐答案

卸弃这些都是我从个人的经验采取了意见的

数据集是如此痛苦的使用我真的不推荐使用它们，除非你有他们的一些特定的需要。我曾在大型.NET 1.0时代项目（数以千计的数据集），我发现他们的难以维护，使用和测试。你，除非你使用强类型数据集，你会花永远保持访问一切与基于阵列的语法。

Datasets are so painful to use I would REALLY not recommend using them unless you had some specific need for them. I have worked on large .NET 1.0 era projects (with thousands datasets) and I find them hard to maintain, use and test. You have to access everything with array based syntax unless you use strongly typed datasets, which you will spend forever maintaining.

我真的建议使用像 NHibernate的的一个ORM。您可以了解更多关于NHibernate的这些屏幕投射。

I would really recommend using an ORM like NHibernate. You can learn more about NHibernate with these screen casts.

如果您有兴趣，可销售的建筑，你应该看看高可扩展性的网站，在这里您将能找到 MySpace的架构的你提到你的问题。

If you are interested in Saleable architecture you should look at the High Scalability web site, where you will be able to find the MySpace Architecture that you mention in your question.

有关数据集更公正的意见，请检查该 MSDN链接 （下面摘要）

For a more unbiased opinion on Datasets please check this MSDN link (summary below)

时使用的

两个数据集和自定义类不   限制你可以以任何方式做，和   既可以用于实现   同样的目标。这就是说，数据集是   为原型梦幻般的工具   应用程序并重新present优秀   建设系统的解决方案   那种紧急预算有限，一   临近最后期限，或短   应用程序生命周期。对于相对   简单的应用程序，自定义实体   增加的可能不必要的水平   复杂。在这种情况下，我建议   你认真考虑使用   数据集。

Both DataSets and custom classes don't limit what you can do in any way, and both can be used to accomplish the same aims. That said, DataSets are fantastic tools for prototyping applications and represent excellent solutions for building systems in a kind of emergency—a limited budget, an approaching deadline, or a short application lifetime. For relatively simple applications, custom entities add a perhaps unnecessary level of complexity. In this case, I suggest that you seriously consider using DataSets.

在一个大的，持久的经济，   复杂的企业系统，该系统采用   数月才能完成，成本   架构设计和实施的   一束集合类是   相对最小，并且发生   只有一次。在以下方面的优点   性能，EX pressivity，   可读性强，易于维护   主要是偿还投资。你是   未绑定的表格呈现   数据。业务规则和定制   实体企业不能总是   适应模样的集合   表。一般情况下，你应该避免   适应数据到数据   容器完全相反，我会说。   最后，使用自定义类，使   更容易单元测试，因为   类和逻辑，更严格   比数据集有关。 在图3中，   你找一个天气表   数据集，类型的DataSet和自定义   相比受到几个因素的实体。

In the economy of a large, durable, complex enterprise system that takes several months to complete, the cost of architecting and implementing a bunch of collections classes is relatively minimal and is incurred only once. The advantages in terms of performance, expressivity, readability, and ease of maintenance largely repay the investment. You are not bound to a tabular rendering of data. Business rules and custom business entities can't always be adapted to look like a collection of tables. In general, you should avoid adapting data to the data container—quite the reverse, I'd say. Finally, using custom classes makes for easier unit testing because classes and logic are more strictly related than with DataSets. In Figure 3, you find a synoptic table with DataSets, typed DataSets, and custom entities compared by several factors.