After watching this video, I don't think I have an understanding of how to actually do DDD, but it covers the very basic concepts at a very high level.
Yes I will probably do another video in the future that breaks down how to actually do it. It is a tricky one though as it is very specific to the domain you are working on.
Sorry to say but it’s difficult to understand with background music and unusual pacing of your talking. Submitting an issue to remove background music and slower the talking pac
@@alexhyettdev Sorry to say but it’s difficult to understand with background music and unusual pacing of your talking. Submitting an issue to remove background music and slower the talking pace
@ReluctantSpirit I have reduced the bg music on my newer videos. I may just remove it completely in future. Unfortunately I can’t change the ones already uploaded.
to me that's exactly what i was looking for. I'm very new to programming and don't know alot about it, but understanding in general what people mean when they talk about DDD helps me understand how they want to build an application
Great video. I am a functional analyst, not a dev, but we must also learn these concepts. And this is a very clear explanation. Please make as much videos about concepts of code design and architecture as possible
Thanks for your concise explanation with easy-to-understand examples. I started reading Creating Software with Modern Diagramming Techniques By Ashley Peacock, and it suggests reading "Domain-Driven Design: Tackling Complexity in the Heart of Software By Eric Evans" to understand DDD. Though I luckily found the title in the O'reilly online library, your video saved my time. I subscribed.
Thank you for sharing the book references. The diagramming book sounds very interesting and just what I am looking for. I'm a junior dev tackling a codename and I've started trying to contribute by diagramming and providing onboarding documentation.
The issue of DDD is that you can design software together with disfunctions you already have in org. Basically, to make it work you need to be ready to change org based on Strategic DDD outcomes.
Hey. I really like your explanations, very clear. Just as a suggestion for future videos, please consider lowering the volume or pick something different for the background music. At times it can be very annoying, specially when using headphones. IE at 7:45, there are some punctuating sounds making it difficult to follow your speech. Otherwise great
Thanks for the feedback. I will see if I can find some background music that is more uniform throughout. It is a tricky one to get right especially if the music has varying sound levels.
Like it. Big part of the video is about Entities and VOs, which are quite common in many designs, I would like to have more of how the domains communicate between each other and what is anti corruption layer about?. Is it Event Broker with adapter layer. How the decoupling is achieved?
Sound practices when designing software and object-oriented patterns used in the right way - I feel like that is lacking. In a lot of places developers go right at the problem before actually checking with the business and designing the software - having a clear system and language for how to structure code.
Yes 100%. It is always tempting to jump straight into the code but it nearly always ends up needing considerable rework later. Reminds me of the “sharpening your axe” analogy.
Great video but I had to keep it in 0.75x atleast to understand. your articulation is very fast or my listening skills are not par :) anyway this is great overview
DDD is more about what you put in each microservice rather than the technology itself. It is possible to use microservices without using DDD. For example you can have microservices for each feature rather than each domain.
Hi there, thank you so much for the video ❤ and i would love to ask you a question. Is DDD still relevant today? Do you think a startup should do DDD? Do large enterprises like Google, Netflix (video case study), Uber and so on use DDD? Sometimes i wonder if some organizations do care about practicing this beautiful methodology as it aims to tackle complexity at the heart of the business. Your response will be highly appreciated. Cheers mate!
Yes they definitely do still use DDD. I am not sure about Google but Netflix and Uber have written articles about using DDD and Hexagonal Architecture: netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749 www.uber.com/en-GB/blog/microservice-architecture/
@@alexhyettdev Thanks mate 👍. I find the links you shared insightful... You probably missed the part where I asked if you think startups should do DDD. I would love to hear your opinion on that too!
I'm pretty new to this and would like your feedback on my thought. I'm studying to be a cloud architect and I'm not much of a coder. When you said an aggregate maintains business invariance is this akin to a policy? making sure specific rules are enforced during deployments.
Yes, it is very similar. An example could be making sure that an API passes its health checks before traffic is routed to it and rolling back the deployment if it doesn't.
Yes, so a domain service is a service that contains core business logic. It is a key component to the application. It might be responsible for processing an order for example in an e-commerce application. Application services on the other hand provide functionality to the system but isn't domain specific logic. This could be writing to a database, logging, and email service or auditing. They are supporting services that most systems have regardless of the domain.
Great video. I am a relatively new dev reading DDD because a coworker suggested it, and found this video because I'm finding the book remarkably dull. (😳) After watching your video, I feel like DDD is somewhat self-evident--in other words, how could you make a Netflix without separating out billing from streaming from whatever else? Please feel free to correct me. :)
Yes I tried to pick an obvious example that everyone would understand. It really depends on how well everyone understands the domain. It is quite common at some companies for engineers to be building software without all the information as the stakeholders aren't willing to share or take the time for it. If you know the domain well then DDD does seem self-evident.
Cool video, but it is not clear that an aggregate is NOT an object. According to Eric Evans: "An aggregate is a cluster of associated objects that we treat as a unit for the purpose of data changes. Each aggregate has a root and a boundary. The boundary defines what is inside the aggregate. The root is a single, specific entity contained in the aggregate. The root is the only member of the aggregate that outside objects are allowed to hold references to." It is the root and the conceptual boundary that defines the aggregate. I think the identity of the aggregate is the identity of the root.
Great video explainning the concepts but it looks to me it's only delegating all the cross-domain work into the least explained anti-corruption layer which still needs knowledge of multiple domain and engineering the system itself. Great practice but it seems just not fitting for a poor team lead trying to not teach everyone everything or handling all the cross-domain work in flesh to make things work in a team not big enough.
Interesting content, but the editing is quite annoying. Every sentence seems to have an edit, a slight zoom, natural space cut out, so it runs into each other and just turns into ... a wall of words. The audience are not gamers with a short attention span, it's people looking for information; we can wait that extra second.
Noted! Yes it is a bit of a balancing act between a boring static man in front of a camera and trying to keep the audience engaged while not making the jump cuts too jarring.
Developers should not be designing- it should be an application/ system architect in close collaboration with a business analyst and product manager. If developers do the design, then we're into a world of change and security issues. Who do you see as having the responsibility for producing the domain design?
I think it depends on the seniority of the developer. Many companies don’t have a system architect role and it is up to the senior developers and engineering managers to design the system architecture. This is usually with the business analysts and product managers as well. In most companies I have worked at there is usually a review team that go over the architecture to sure that all security considerations have been addressed.
I've got the book title, and I will read it, thanks! But your fast and compressed 'blah-blah-blah' is just absolutely useless (it was, for me). For the Foreign speakers...
It's interesting, for sure, but you're speaking too fast and with very 'native English'. Your should speak slower and with more 'common English', acceptable for everyone. I've switched on Subtitles to understand your words from the Text, not from your voice words. Sorry...
No worries, I have tried going slower in newer videos. It is more to do with nerves more than anything else. Speaking to a camera really isn't natural!
I am not a native English speaker. I am student. I don't speak English well. Your presentation is good but it is something difficult to me to understand your accent and fluency. I suggest you to speak little more slow and fulfill the word you are saying in pronunciation. Good luck.
Thanks for the feedback. I speak a lot slower in person. It is something about being in front of the camera! I am sure I will get better with practise.
Hi Alex, thank you for your video. I like the British English pronunciation. I lived for 5 months in England, at first it was a little difficult to keep up with the native speakers, I was able to learn their accent, however there are many accents in the UK. Your videos help me a lot to remember that particular English!! thank you.
Don’t change your speed it works well without the speed change on Google. If you increase or decrease it it will cause weird lag or upscale issues I think….
