The mainstream thought on Domain Driven Design is about Entities, Value Objects, Aggregates, Repositories, Services, Factories... all kinds of technical patterns. Because of this, most don't think they need Domain Driven Design because it's complicated for their domain. Why would you need all that "stuff"? Well maybe you don't! In a large system, modeling your domain, defining boundaries, and how they relate is far more important than concerning yourself with if you're using the Repository pattern correctly. 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw 💥 Join this channel to get access to source code & demos! null 🔥 Don't have the JOIN button? Support me on Patreon! https://www.patreon.com/codeopinion 📝 Blog: https://codeopinion.com/stop-doing-dogmatic-domain-driven-design/ 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 0:00 Intro 0:38 Technical Pattern Focus 2:53 Context is King 5:41 Resources https://github.com/ddd-crew/bounded-context-canvas https://github.com/ddd-crew/aggregate-design-canvas https://www.eventstorming.com/ #softwaredesign #domaindrivendesign #softwarearchitecture