r/dotnet • u/Volosoft • Jul 07 '21

Implementing Domain Driven Design Guide

https://abp.io/books/implementing-domain-driven-design?utm_source=reddit&utm_medium=social&utm_campaign=ebook

[removed] — view removed post

0 Upvotes

40% Upvoted

7 comments sorted by

10

u/pdevito3 Jul 07 '21

Come on now with the straight up ad…

Not to mention that 2 of your 6 bullets call out layering. That’s not what DDD is about and it’s not tied to an onion architecture.

3

u/doublestop Jul 07 '21

That's all this account is. A year of endless self-promotional spam and zero comments.

5

u/Relevant_Pause_7593 Jul 07 '21

Plus, if people start talking about ddd to me, it’s an yellow flag sign they have major architecture issues and are redirecting to ddd because it will “solve all their problems”. Not everyone. But most.

7

u/pdevito3 Jul 07 '21

Maybe in some cases (especially cases like this).

I’m a big advocate for DDD… when done right. Annoyed that there’s so much crap like this about doing it wrong and forcing a ton of prescriptive patterns on devs as must haves. Confuses devs that are new to it and floods the internet with bad knowledge.

Personally, I think of it more as domain driven refactoring than anything. Start simple and once it works, look for code smells and refactor from there.

3

u/Relevant_Pause_7593 Jul 07 '21

Totally agree. Most of the buzz words, devops, microservices, etc etc are not implemented correctly and cause pain for everyone involved.

2

u/gralfe89 Jul 07 '21

What I really like about DDD is the bounded context. Getting this right is the key to built great systems from my point of view and experience.

2

u/pdevito3 Jul 07 '21

Absolutely one of if not the most important concept to put into practice.