In this video I kinda answer this question. th-cam.com/video/gtZIaSxRkS4/w-d-xo.html The idea is that using DDD you should map a microservice to a Bounded Context and not a single Entity. You need cohesion within the service and low coupling with the other contexts. I always remain shocked when I hear organizations mentioning they have systems with 1500+ services as I cannot fathom how small they must be to get to that number (e.g. Netflix, Financial Times...).
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.
I think modern frameworks reduced barrier to entry when it comes to programming. A junior programmer can write an API and persist data in few minutes using Spring Boot and their Initializr. But that also means that less time is spent on modelling. The result is anemic models. For example I often see validation in the controller layer while the model underneath is just getters and setters. I think it depends a lot on the individuals you get in your team.
@MarcoLenzo that's Wright anyone can persist data using orm but not every one can design a hole system . For me personally big project not following ddd and using anemic models is potentially a failing project
Yeah I know. In most recent videos I manually corrected all the subtitles and reduced the background music. I'll invest time fixing the subtitles also on older videos. Thank you for the honest feedback. It's really appreciated
Yes. It was one of my first videos and I made a mistake putting the background music too loud. In recent videos I either put it lower or remove it completely.
Man, I'm so happy I found your channel.
Thank you!
This is a really, really good introduction to DDD concepts for someone looking into it for the first time. Thank you!
Glad it was helpful!
been a week trying to get my head around. this is very simple to understand
Let me know if you are interested in a particular topic and I will do a video on it.
That was really good content. Explained in a straight forward and easily digestible way. Really appreciate the book reference as well. Thank you.
Thank you for the support
Your videos are concise and animations very well made! Bravo. I am learning so much?
Happy to hear that! Recently I had to take a small break but I'm coming back with more educational content!
Great content. Concise and very rich.
Thank you very much for the feedback!
That was very good and understandable, thank you! :)
Thank you 🙏
Thank you for this great content. Please share videos on Solid, OOP and clean code explanation.
I will. Thank you for the feedback 🙏
Very well explained thankyou
Thank you 🙏
can you compare DDD to Entity Trap? DDD will split system by each business logic together, then Entity Trap is doing that too?
In this video I kinda answer this question. th-cam.com/video/gtZIaSxRkS4/w-d-xo.html The idea is that using DDD you should map a microservice to a Bounded Context and not a single Entity. You need cohesion within the service and low coupling with the other contexts. I always remain shocked when I hear organizations mentioning they have systems with 1500+ services as I cannot fathom how small they must be to get to that number (e.g. Netflix, Financial Times...).
Great information ! thanks keep up the good work
Thank you! It's really appreciated!
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.
I think modern frameworks reduced barrier to entry when it comes to programming. A junior programmer can write an API and persist data in few minutes using Spring Boot and their Initializr. But that also means that less time is spent on modelling. The result is anemic models. For example I often see validation in the controller layer while the model underneath is just getters and setters. I think it depends a lot on the individuals you get in your team.
@MarcoLenzo that's Wright anyone can persist data using orm but not every one can design a hole system . For me personally big project not following ddd and using anemic models is potentially a failing project
Very helpful video for introduction to DDD. Just adjust a background music as your english pronunciation is hard to catch and requires polish.
Yeah I know. In most recent videos I manually corrected all the subtitles and reduced the background music.
I'll invest time fixing the subtitles also on older videos.
Thank you for the honest feedback. It's really appreciated
the sound in the background is disturbing
Yes. It was one of my first videos and I made a mistake putting the background music too loud. In recent videos I either put it lower or remove it completely.