This is fantastic. Great explanation. I've seen this explained elsewhere in a book I think and for the life of me can't remember which but this is an excellent summary.
Your Videos containing explanations in few minutes what workshops trying to say in hours. Thank you very much! Keep up! I will share it within my Team :)😊
It's really good video, but the more pattern I learned, the more traditional way I would decide to use. I've been implementing DDD and Microservice for years, and I found traditional design always win, and you don't need to seek for a new pattern to fix the patterns.
I'm also curious, what is the method you use? Also I think you're implying that there are other situations within DDD/microservices where more modern patterns are perhaps no better than traditional patters. Could you give an example or two as to what those are too?
Thanks! I'm glad you enjoyed the video. I assume you mean a traditional monolithic centralised application? That is a perfectly valid approach too, but it has its downsides. There's always a trade-off. If you're interested, check out my video comparing these here czcams.com/video/6-Wu178sOEE/video.html
1. The Anemic model, Monolithic, or even MVC are the "traditional ways" I meant. It sounds old but it always "get things done". 2. Microservices or DDD are highly ideal in terms of design, but the implementation just not align with reality. Aggregate Root is a great concept, but it's not when you are trying to save/update it. There are still a lot I wanted to talk about, but instead of following DDD mentally, I'm starting to use part of the concept to complement my Monolithic, I found it works the best. I just won't use Microservice / DDD / Event-driven *from the ground up* to lost in the "Pattern Maze" again 💀💀 To know if you are solving a "problem" or a "problem that doesn't exist" is also a puzzle.
This is fantastic. Great explanation. I've seen this explained elsewhere in a book I think and for the life of me can't remember which but this is an excellent summary.
Excellent explanation! Visual, concise but still explaining all the important matters.
Please take a look at spring modulith, it implements all the concepts you described in all your videos !
Your Videos containing explanations in few minutes what workshops trying to say in hours. Thank you very much! Keep up! I will share it within my Team :)😊
Your videos are so good. They're concise and informative.
Excellent video displayed in an animation, thanks a lot
Always the best videos.
Cheers! Great to see you here, as always!
Great explanation, thank you!
Great video! Very concise and informative
amazing video!
Love your videos, keep going!
What toolset are you using to create these great videos?
I supposed PowerPoint is one of them.
Exactly - export slides as video, record my voice and make background music in Ableton, then retime the video to the audio with DaVinci Resolve
Nice!
thanks
It's really good video, but the more pattern I learned, the more traditional way I would decide to use.
I've been implementing DDD and Microservice for years, and I found traditional design always win, and you don't need to seek for a new pattern to fix the patterns.
What’s the traditional way?
.@@robotrabbit5817maybe a monolith and scailing verticality?
I'm also curious, what is the method you use?
Also I think you're implying that there are other situations within DDD/microservices where more modern patterns are perhaps no better than traditional patters. Could you give an example or two as to what those are too?
Thanks! I'm glad you enjoyed the video.
I assume you mean a traditional monolithic centralised application? That is a perfectly valid approach too, but it has its downsides. There's always a trade-off. If you're interested, check out my video comparing these here czcams.com/video/6-Wu178sOEE/video.html
1. The Anemic model, Monolithic, or even MVC are the "traditional ways" I meant.
It sounds old but it always "get things done".
2. Microservices or DDD are highly ideal in terms of design, but the implementation just not align with reality.
Aggregate Root is a great concept, but it's not when you are trying to save/update it.
There are still a lot I wanted to talk about, but instead of following DDD mentally,
I'm starting to use part of the concept to complement my Monolithic, I found it works the best.
I just won't use Microservice / DDD / Event-driven *from the ground up* to lost in the "Pattern Maze" again 💀💀
To know if you are solving a "problem" or a "problem that doesn't exist" is also a puzzle.