Domain Layer Structure & Skeleton | Clean Architecture & DDD From Scratch Tutorial | Part 13

Today we'll implement the domain layer skeleton in our Buber Dinner application!

Connect with me on 'em socials:

#dotnet #csharp #ddd

[TurgayTuerk]

I can't even imagine how much effort it takes to prepare a series of tutorials on this topic. Thank you so much! looking forward for the next one!

[andreaskonomis]

Had read the blue book till a point and the argument regarding the difference an organized namespace/folder structure makes stuck with me, but hadn't come across from anyone else such an example before. Kudos! Keep rocking!

[ibrahimkoz]

I cannot explain how much I appreciate your work. This is such an incredibly useful and decent series.

[mdsahidulhussain]

I have been following this series from day 1. Its very informative. I really appreciate your work. Thanks for sharing your knowledge.

[DanielOliveira-hduc]

I've never seen these approaches before, it's super clean, thanks for sharing with us!

[avecesar]

I can´t thank you enough... I've learned a lot of concepts, but the most valuable lesson has been the fact that not every domain fit into this practisess; complexity is a choise, some times.

[gtejeda]

Excellent explanation and series so far, good job!

[tomheijtink]

We have been doing something similar. One difference is that we put all the aggregates in a folder called Aggregates. So the common folder doesn't get mixed up with the other aggregate folders.

It works well, and have so not noticed any real downsides to this approach. One interesting idea is to use the new file nesting capabilities in visual studio. This could in theory do away with many folders. And you would be able to nest a value object for a specific entity.

[robertogonzalorodriguez]

Great video, Amichai! Looking forward to the persistence implementation. Thank you very much.

[ti_doo]

Awesomely great video, well structed and presented. Thanks a lot!

[Emmap]

This is a GREAT JOB!!! I love this series, was fantastic thank you!

[amantinband]

Curious to hear what you thought about the implementation part of this video! Was it too fast? Too slow? Would you have preferred I hadn't skipped writing out the aggregate parts we already covered? Also, would you have preferred I actually wrote out the entire domain?

[gui.ferreira]

It's amazing how the folder structure can change the way how you approach all other decisions. 👏👏👏

[ylazerson]

great video on a complex subject - thanks!

[hugoribeiro]

What a nice series you're creating, Amichai! Congrats for the great work. One thing I was wondering is if u re gonna make something to not repeat the create/update props in each needed class.

[npee]

I LOVE this series so far. Thanks for your effort in making it so smoothe and enjoable.
Is there any chance that (in future) you could add some kind of keystrokes monitoring to your films and vs code shortcuts settings (your workflow is amazing)?

[rkswmff]

Hi Amichai, Great Video really like the series, I think based on the gist in the description that maybe you should have an common entity with created/updated DateTime properties that inherit from the base entity class and then we can have less duplication of code to have it on each Entity we creating

[brandonbailey]

Awesome playlist! are you planning on making any more videos for this series?

[broodja]

Thank you so much, Amichai, great work, keep it up. I personally enjoy you voice pitch and pace, make it much more enjoyable to listen complex explanitions.
Hope this time I can FINALLY make it straight and logical in my head.
P.S.: Can you say what's that suggetion tool at 8:30?

[pdevito]

Always fun seeing how people organize this. Definitely agreed on colocation!

Curious to see how the value objects will work for the foreign keys and what interactions with those and their entities will look like. Seems like you might need some interesting helpers on the value objects to facilitate interactions, but maybe there’s some other patterns to help here.

Regardless, fun watch as always. Thanks for sharing 🍻