DDD is not about code

👨‍💻 Learn Test-Driven Development with Laravel!
tddwithlaravel...
Sign up to 30 Days of Laravel 👉🏻 30daysoflarave...
👨‍💻 Sign up to my newsletter and receive PHP, JS and Laravel news in a weekly-basis:
subscribe.mate...
🎉 Party up:
/ mateusjatenee
/ mateusjatenee
/ mateusguimaraes
Thanks for watching!

[@tmanley1985]

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.

[@AntonioFalcaoJr-yj2dx]

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.

This is an excellent comment. Thank you!

[@MattRobinsonDev]

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.

100%!

[@mr-maschi]

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]

I think ddd stands for Dutch developer driven 😂they seem to have a strong opinion on this....

Hahahaha