DDD Explained in 9 MINUTES | What is Domain Driven Design?

Domain Driven Design (DDD) is one of the pillars of object oriented software development. You must understand it really well if you want to produce future proof code and designs. In this video, we cover the basic of Tactical and Strategic DDD.

A domain is the subject of a software system or application. A model is a simplified and structured abstraction that maps and documents everything of interest in the domain. In the tactical design phase, we use Entities, Value Objects, Associations, Aggregates, Factories and Repositories. In the strategic design phase, we use Bounded Contexts and Context Maps.

🤓 There's more on my website! (articles, scripts, code snippets, etc...): 🤓

🤝 Connect with me: 🤝

👌Get a CodeCrafter Discount 👌

0:00 Intro
1:53 Tactical DDD
6:39 Strategic DDD
9:12 Conclusion

#ddd #softwaredevelopment #softwarearchitecture #softwaredesign

[jonbellamy]

This is a really, really good introduction to DDD concepts for someone looking into it for the first time. Thank you!

[powell.christopher]

That was really good content. Explained in a straight forward and easily digestible way. Really appreciate the book reference as well. Thank you.

[tassisto]

Man, I'm so happy I found your channel.

[HideBuz]

Your videos are concise and animations very well made! Bravo. I am learning so much?

[sandorfarkas]

That was very good and understandable, thank you! :)

[DevOpsHasan]

Thank you for this great content. Please share videos on Solid, OOP and clean code explanation.

[IasonOrlandosOx]

Great information ! thanks keep up the good work

[tranhuy]

can you compare DDD to Entity Trap? DDD will split system by each business logic together, then Entity Trap is doing that too?

[farrukhahmedsid]

Very helpful video for introduction to DDD. Just adjust a background music as your english pronunciation is hard to catch and requires polish.

[tharun]

Spent a lot of time learning tactical design only to realise that no real projects actually use this design approach. I primarily worked on Java Spring boot projects and unfortunately, it borrows DDD terms like Entities, Repositories but uses them for different purposes. For ex: Java's entity is the Database table rather Domain entity. Nevertheless, I find the ideas & intentions of DDD to be useful in a generic sense.

[anzeigeistraus]

the sound in the background is disturbing