Enforcing Module Boundaries in Code

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface

• Open learner-facing unit
• Curriculum path: content/curriculum/architecture/semester-07-architecture-ddd/module-02-architecture-patterns-modular/concepts/cluster-02-modular-monoliths-and-component-based/06-enforcing-module-boundaries-in-code-primary.md
• App: architecture
• Semester: semester-07-architecture-ddd
• Module: module-02-architecture-patterns-modular
• Unit kind: concept
• Curation level: module_curated

Learning objectives

• Explain Enforcing Module Boundaries in Code as a choice among modular structures and coupling tradeoffs, not as a pattern-name checklist.
• Use Enforcing Module Boundaries in Code to predict how change, testing, deployability, and team coordination will behave in a real codebase.
• Use clean-architecture, fundamentals-of-software-architecture to connect the learner page to modular boundaries, dependency direction, and architectural style tradeoffs.

Prerequisites

• Comfort with architecture fundamentals and quality-attribute reasoning from module 01.

Source books

• clean-architecture
• fundamentals-of-software-architecture

Source routes

Clean Architecture

• /books/clean-architecture via Martin: Package by Component

Fundamentals Of Software Architecture

• /books/fundamentals-of-software-architecture via Richards & Ford: Governance and Fitness Functions (from M01), Richards & Ford: Modularity

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

• Martin Fowler: Monolith First (read_if_stuck) - Reinforces that architectural style choice is a tradeoff and should follow real constraints, not fashion.
• Simon Brown: Modular Monoliths (optional_deep_dive) - Helps connect modularity concepts to concrete structure and deployment choices.

AI companion modes

• Explain simply
• Socratic tutor
• Challenge my understanding
• Diagnose my confusion
• Connect forward / backward

Source-of-truth note

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Enforcing Module Boundaries in Code, and treat outside material as supporting enrichment only.