DDD is not about code

  Рет қаралды 1,484

Mateus Guimarães

Mateus Guimarães

Күн бұрын

Пікірлер: 8
@tmanley1985
@tmanley1985 8 ай бұрын
I think it's a useful academic exercise to try and apply things that may be traditionally within the purview of software engineering to other domains. I try to remember to do this when I'm learning something and I call it "chasing the links", meaning I'm trying to find relations to other things so that I can enrich my own understanding of whatever it is I'm trying to study.
@MattRobinsonDev
@MattRobinsonDev 8 ай бұрын
Fully agree, I was at phpuk recently and there was a talk on DDD. I expected it to be code related & structure etc but it was all about how you implement it within a business from the actual design process. It was essentially all the steps before you get to the code which was spoken about. They spoke about how the code doesn't really matter, as long as you use the principles and everything else you can even add it to legacy codebases one domain at a time, but use the existing structure etc instead of battling it.
8 ай бұрын
100%!
@AntonioFalcaoJr-yj2dx
@AntonioFalcaoJr-yj2dx 8 ай бұрын
Just a small, but significant, adjustment to your statement: Ubiquitous language is not shared and agreed upon across an entire organization or system (domain) but for each Bounded Context. Otherwise, we would not benefit from maintaining context-sensitive entities (eventually consistent), thus achieving a real level of independence. This independence can provide modularization. A subdomain can be complex enough to require more than one bounded context to address its concerns effectively. Still, a subdomain is a strong candidate for a module or microservice.
7 ай бұрын
This is an excellent comment. Thank you!
@mr-maschi
@mr-maschi 3 ай бұрын
Why always black and white ? DDD is both. Even if you only have the strategic part implemented, it makes the code so so so much more readable and maintainable. Even if you are not on point with the ubiquitous language. Of course it would be perfect to have all aspects implemented, but I see it more like I see Scrum. It's a philosophy and a lego box. Take out and use what you think is useful for the team and company.
@lassestube
@lassestube 8 ай бұрын
I think ddd stands for Dutch developer driven 😂they seem to have a strong opinion on this....
8 ай бұрын
Hahahaha
What I do before coding complex features
20:35
Mateus Guimarães
Рет қаралды 2,3 М.
DDD is not enough: the future of software development - Dave West - DDD Europe 2020
15:30
The most powerful way to use Eloquent
11:51
Mateus Guimarães
Рет қаралды 5 М.
The dangers of events and observers in Laravel applications
29:06
Mateus Guimarães
Рет қаралды 1,8 М.
What’s Up with Laravel? It’s Everywhere, and Here’s Why!
6:22
Why Everyone Loves Zustand
29:27
Theo - t3․gg
Рет қаралды 107 М.
Clean Code is SLOW But REQUIRED? | Prime Reacts
28:22
ThePrimeTime
Рет қаралды 323 М.
PHP-FPM vs Swoole execution model
15:36
Mateus Guimarães
Рет қаралды 7 М.
How to properly integrate with 3rd party providers
16:27
Mateus Guimarães
Рет қаралды 2,2 М.
Using fake objects in automated tests
15:50
Mateus Guimarães
Рет қаралды 2,3 М.
Thinking about Aggregates in Active Record
19:22
Mateus Guimarães
Рет қаралды 2,9 М.
Why is Javascript so advanced yet behind?
9:05
Mateus Guimarães
Рет қаралды 965