Hi All,
First of all thanks for this great asp.net boilerplate. I have worked on asp.net for years and I have not found any better. I see asp.net boilerplate follows DDD aproach. I see however it is generating anemic domain model instead of rich domain models. Isn't this an anti-pattern according to DDD?
5 Answer(s)
-
0
Hi,
Yes, it is (<a class="postlink" href="http://www.martinfowler.com/bliki/AnemicDomainModel.html">http://www.martinfowler.com/bliki/Anemi ... Model.html</a>). But ABP does not force to anemic model. Maybe you're talking about sample projects. They are just simple samples those don't contain any significant business logic. You can implement full domain driven design using ABP. It provides a good infrastructure for that.
-
0
True, ABP does not force Anemic but IMO ABP is also to demo for best practices. It means that adding at least basic AggregateRoot to show how to do things properly before project becomes too large will be very useful. Anyway it's just my 5c.
-
0
I agree that. I'll try to prepare more rich DDD examples in the future.
-
0
Hi
May i know is there any example for AggregateRoot in the sample project? Please advise. Thanks a lot
-
0
Hi,
Sample projects does not contain any AggregateRoot but there is one in our unit tests. You can check it if you haven't seen it alread <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/blob/a706b7e8f497a4afe2bb746892fd6c010b0875fc/test/Abp.EntityFrameworkCore.Tests/Domain/Blog.cs">https://github.com/aspnetboilerplate/as ... in/Blog.cs</a>
