Distributed Architecture Fallacies Applied to Style Choice
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-05-choosing-a-style/14-distributed-architecture-fallacies-applied-to-style-choice-supporting.md - App:
architecture - Semester:
semester-07-architecture-ddd - Module:
module-02-architecture-patterns-modular - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Distributed Architecture Fallacies Applied to Style Choice as a choice among modular structures and coupling tradeoffs, not as a pattern-name checklist.
- Use Distributed Architecture Fallacies Applied to Style Choice to predict how change, testing, deployability, and team coordination will behave in a real codebase.
- Use
fundamentals-of-software-architectureto 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
fundamentals-of-software-architecture
Source routes
Fundamentals Of Software Architecture
- /books/fundamentals-of-software-architecture via
Richards & Ford: Monolithic versus Distributed Architectures (the fallacies chapter)
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. Its canonical source backbone is the referenced book fundamentals-of-software-architecture, and outside material should only clarify or strengthen that backbone.