DTO objects are used to deserialize data into objects from different sources. Those objects are NOT your Model (POCO) objects. You need to transform those objects into your Model (POCO) objects. The transformation is mostly a copy operation. You can fill those POCO objects directly from the source if its an internal source, but its not adviceable if its an external source. External sources have API's with descriptions of the Schema they use. Its much easier then to load the request data in an DTO and after that transform those in your POCO's. Yes its an extra step, but with a reason. The rule is to load the data from your source in an object. It can be JSON, XML whatever. When loaded then transform that data in what you need in your model. So most of times the DTO is an object image of the external source. Sometimes you even get the Schema's of the source providers then you can deserialize even easier, XML works like that with XSD's.

DTO objects are used to deserialize data into objects from different sources. Those objects are NOT your Model (POCO) objects. You need to transform those objects into your Model (POCO) objects. The transformation is mostly a copy operation. You can fill those POCO objects directly from the source if its an internal source, but its not adviceable if its an external source. External sources have API's with descriptions of the Schema they use. Its much easier then to load the request data in an DTO and after that transform those in your POCO's. Yes its an extra step, but with a reason. The rule is to load the data from your source in an object. It can be JSON, XML whatever. When loaded then transform that data in what you need in your model. So most of times the DTO is an object image of the external source. Sometimes you even get the Schema's of the source providers then you can deserialize even easier, XML works like that with XSD's.

POCO遵循面向对象的规则。它应该(但不必)具有状态和行为。POCO来自于POJO，由Martin Fowler创造。他使用术语POJO作为一种方式，使其更性感地拒绝框架繁重的EJB实现。在. net中，POCO应该在相同的上下文中使用。不要让框架支配你的对象设计。

DTO的唯一目的是传输状态，不应该有任何行为。请参阅Martin Fowler对DTO的解释，以获得使用此模式的示例。

区别在于:POCO描述了一种编程方法(老式的面向对象编程)，而DTO是一种使用对象来“传输数据”的模式。

虽然您可以像对待dto一样对待poco，但是如果您这样做，就会有创建贫血域模型的风险。此外，还存在结构上的不匹配，因为dto应该被设计为传输数据，而不是代表业务领域的真实结构。这样做的结果是dto往往比您的实际域更平坦。

在任何合理复杂的域中，最好创建单独的域poco并将它们转换为dto。DDD(领域驱动设计)定义了反腐败层(这里有另一个链接，但最好的方法是购买这本书)，这是一个很好的结构，使隔离清晰。

DTO的一个主要用例是从web服务返回数据。在这种情况下，POCO和DTO是等价的。POCO中的任何行为在从web服务返回时都将被删除，因此它是否具有行为并不重要。

下面是一般规则:DTO=邪恶和过度工程软件的指示器。少= =好。“企业”模式已经摧毁了Java EE世界中许多人的大脑。请不要在。net领域重复这个错误。

甚至不要称它们为dto。他们被称为模型....句号。模特从来没有行为。我不知道是谁想出了这个愚蠢的术语DTO，但它一定是一个。net的东西，这是我所能想到的。想想MVC中的视图模型，同样的东西，模型是用来在层与层之间传递状态的服务器端或线上传输，它们都是模型。属性与数据。这些是你传递的模型。模特，模特。就是这样。

我希望DTO这个愚蠢的术语能从我们的词汇表中消失。