Domain Vs Subdomain Ddd

In studying domain driven design ddd i ve come across the concept of subdomain but i think i don t get it yet.

Domain vs subdomain ddd. While sub domains delimit the applicability of domains bounded contexts delimit the applicability of domain models. When you re searching for a domain name there are all kinds of terms that you ll come across. There is a lot of confusion around these terms especially when one starts reading about domain driven design. Domain subdomain domain vs subdomain domains subdomains difference domain names are mainly used as names for websites.

All of this can be a little overwhelming when you re just getting started. My first understanding of this was that a subdomain is a subset of the domain of the application. In other words it s a partition of the problem space. In short instead of having to type each website s ip into our browsers domain names give websites their own good looking name that can be easily memorized and used by everyone.

The relationship between sub domains and bounded contexts however is deeper still. As such the bounded context is within the solution space. 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. Domain vs sub domain vs bounded context in ddd in today s blog post i will be discussing some of the key terms in domain driven design.

The goal of a domain driven design is an alignment between the domain and the software. In simple terms a subdomain is a subpart of the domain.