How are domains and subdomains used in DDD?
DDD requires the decomposition of the Domain into Subdomains, which facilitates our understanding. In this way, we are able to separate what in fact generates value and financial return for the company, and thus, strategically we can put our best efforts in that part of the Domain.
Which is the most vital concept of DDD?
Domain is the most vital concept of DDD, understanding what is Domain is essential for us to accomplish what we call ‘ Domain Distillation ‘, which we will address with example in future Posts.
Can a domain be divided into subdomains?
Regardless of the size of the company, every Domain can always be divided into Subdomains, by doing this we divide the entire complexity of the Company’s Domain into smaller parts, and we will have domain experts who will understand the aspects of the business very well because it is a specific Subdomain. There are three types of Subdomains:
Do you Design Your Domain from the domain?
It is from the Domain that we design our Domain Models, which are solutions that seek to meet the needs of the Domain. It is a mistake to think that we can create a single Domain Model for the entire company, if you try to do that it will surely fail.
Who are the experts in Domain Driven Design?
The experts/resources that this architecture is based on are Jason Taylor, Julie Lerman, Steve Smith, Jimmy Bogard, Matthew Renze, Vladimir Khorikov, Greg Young, Dino Esposito, and finally the Microsoft e-book, .NET Microservices: Architecture for Containerized .NET Applications.
How to avoid duplicate models in Domain Driven Design?
It should be reusable to avoid any duplicate models and implementations of the same core business domain elements. The model should be designed loosely coupled with other layers in the application, meaning no dependencies on the layers on either side of domain layer (i.e. database and facade layers).