# Alignment of Bounded Context and Subdomain > [!Note] > Strive to align each [[Bounded Context]] with its corresponding [[Subdomain]], and when perfect separation isn’t feasible, segregate Supporting Subdomains** within the same context and enforce boundaries through **independent modules**. The **optimal objective** in [[Domain-Driven Design]] is to have one [[Bounded Context]] per [[Subdomain]], ensuring that each area remains focused on its unique set of concepts and rules. When practical constraints prevent full isolation, treat the Supporting Subdomain as a distinct slice within the larger context, clearly marking its boundaries in both the model and the code. Finally, adopting **independent modules** allows teams to maintain a conceptual separation even when multiple subdomains coexist in a single codebase, preserving clarity and reducing the risk of accidental coupling. --- ## References - Vernon, V. (2016). _Domain-driven design distilled_. Addison-Wesley Professional. - Vernon, V. (2013). _Implementing domain-driven design_. Addison-Wesley Professional. - Khononov, V. (2021). _Learning domain-driven design: Aligning software architecture and business strategy_. O’Reilly Media. - Alammar, J., & Grootendorst, M. (2024). _Hands-on large language models: Language understanding and generation_. O’Reilly Media. - Evans, E. (2003). _Domain-driven design: Tackling complexity in the heart of software_. Addison-Wesley Professional. - Millett, S., & Tune, N. (2015). _Patterns, principles, and practices of domain-driven design._ Wrox.