使用STE与POCO进行DDD [英] DDD using STE vs POCO

问题描述

使用Microsoft技术(我们可以完全控制所有组件)使用DDD开发n层应用程序(更好的DDDD，因为我们正在使用WCF)，因此最好的选择似乎是STE vs POCO(这最后一个迫使使用DTO).这是正确的?您认为在需要的地方将STE与DTO一起使用是合理的吗?

Developing n-layered application with DDD (o better DDDD because we are using WCF) using Microsoft technology (where we have full controll of all component), the best choise seems to be STE vs POCO (this last one force the usage of DTOs). That's right? In your opinion make sense the usage of STE with DTOs where we need them?

谢谢.

推荐答案

我真的可以推荐Julie Lerman的编程实体框架 .她深入介绍了简单的poco，dto和自我跟踪实体.描述了优点和缺点.但是偏离路线很大程度上取决于应用程序要求和个人品味.

I really can recommend Julie Lerman's Programming Entity Framework. She goes in depth about simple poco's, dto's and Self Tracking Entities. Advantages and disadvantages are described. But off course depending a lot on application requirements and personal taste.

所以我不能给您确切的答案，因为问题是一般性的.但是，阅读本书应使您对可能的替代品有所了解，并可以帮助您做出此类设计决策.我正在将自我跟踪实体与业务访问层，服务层，WCF，Win/WPF客户端结合使用.并可能在将来使用ASP.NET进行扩展

So I can't give you an exact answer because the question is to general for that. But reading the book should give you a taste of the possible alternatives and can help you in making these kind of design decisions. I'm working with Self Tracking Entities in combination with a Business Access Layer, Serive Layer, WCF, Win / WPF clients. And expanding it in the future most probably with ASP.NET

这篇关于使用STE与POCO进行DDD的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！