2. What is Domain Driven Design?

How do you start designing microservices? The answer is Domain Driven Design.
In this tutorial, I go through "What is Domain Driven Design?" and high-level overview of what it provides us. Domain Driven Design is well respected in developers community and the best way to start designing a microservices architecture. It's a thought. It's OOP done right.

This lecture is a part of crash course on "Mastering the art of designing Microservices Architecture". For full crash course follow:

This crash course is a part of an 8 crash course series called ""Complete Guide To Creating Scalable Backend Infrastructures". The intro to complete series can be found here:

Please like, subscribe and share for spreading the love of learning. Follow us on:

[visamtechtalk]

very nice video. Why did you stop videos ? You are wonderful guy and you explained DDD very well . Try to continue sharing the videos

[purtelo]

DDD looks just like a buzzword - this is default design type that most of people use without giving it a label. What are other types of design that are not DDD?

[paulm]

So almost no explanation of what DDD actually is.

[TrulyLordOfNothing]

can I know what is the sound track in the beginning of the video?

[FokwaDivine]

Thanks for the short and clear explanation

[Melvinx]

Thank you YouTube for recommending this and thank you Anshul for creating this series!

[tqwewe]

That quote at the very end is funny af lmao I didn't expect it

[matt-g-recovers]

Hey, this is a good little playlist you got here!
It is getting to be long in the tooth date wise only, information is still very relevant in 2022.
Would like to learn what you have learned since? Anything change?

[claudiucosar]

Good series! i went couple of years away through both the long runner(DDD) and the quick one(QDDD). what i don't quite understand is the Steve's quote that says: "it's not customer job to know what they want..."
IMO i would replace the "WHAT" with "HOW". We can consult the client and provide various solutions but telling the customer "WHAT" he wants is like me running his own business. I guess that quote refers strictly to building a mature product in which sense indeed one can drive the customer in selling various features or even drive the market directions with a set of features THE product exposes. In vast majority of cases we are working in projects wihch don't particularly target PRODUCT based projects, but more like a services oriented projects... in this last case, it's pretty hard to adhere to that quote, because customers know very well or at least should know how to stand up the competition....my 2 cents.

[ardonjr]

This was a good exlanation, Thanks for his video.

[GG-uzus]

Shouldn't the services be drawn outside the subdomains?

[sammokhtari]

Thank you very much for this very clear presentation. I enjoyed the ending jokes too ;)

[denniscooper]

Can you tell me, what does Domain Driven Design means at code level? Or is it just for architects ?

[morgadoapi]

Thanks for your efforts on explaining DDD. Keep up the great work.

[ben_jammin]

Dude, flawless intro! Liked and subscribed.

[Himankfulara]

We are using DDD in our company. But I have started exploring it in depth recently. At the start of video you mentioned that DDD is used for designing microservices. Is DDD only approach to desgin microservices or are there other approaches too ?

[zobinhuang]

Very clear explaination of DDD, learn a lot from this, thx :)

[jayantvedwan]

Thank You.
It helps ... before this, I saw a video on the same topic and it's not even a video, there was just a virtual lady whose audio is repeating only the bookish Definition of DDD. Hate That
anyways thanks, Guys.
There are no Videos on the Internet on these topics. Especially shorter videos.
Really appreciated.

[ythalorossy]

Thank you very much for share the knowledge. But please remove the background music.

[tiagodagostini]

aaa why people keep repeating that design patterns tell you how to make something? Go read the original papers where they were proposed, it is explicitly stated they are NOT for that. They are for creating a common pattersn for communicating how something has been done and so that what has been done can be understood f aster (because you can use a pattern name and everyone will know what you mean).

To use design patterns as a guide to how to do something is going EXACLTY against DDD, you are twisting youir probolem so you can fit design patterns... that is BAD VERY BAD.