How to avoid anemic domain models, or when to move methods from the entities into services
问题 I have a common scenario that I am looking for some guidance from people more experienced with DDD and Domain Modeling in general. Say I start out building a blog engine, and the first requirement is that after an Article is posted, users can start posting Comments on it. This starts fine, and leads to the following design: public class Article { public int Id { get; set; } public void AddComment(Comment comment) { // Add Comment } } My MVC Controller is designed like this: public class