الفصل 3
Application Architecture
Compare layered, clean, hexagonal, modular, vertical-slice, CQRS, and domain-driven approaches.
ما ستصبح قادرًا عليه
- Explain the architectural purpose of Layered Architecture.
- Evaluate trade-offs across Layered Architecture, Clean and Onion Architecture, Hexagonal Architecture.
- 1
Layered Architecture
The most widely used application structure there is: what layering actually buys, the difference between closed and open layers, and the two failure modes that give it its reputation.
0/2 lessons6 questions32 min - 2
Clean and Onion Architecture
Concentric rings with dependencies pointing inward: what that actually buys, how clean and onion differ, and the three ways teams implement the diagram without getting the benefit.
0/2 lessons6 questions31 min - 3
Hexagonal Architecture
Ports and adapters: one application core with two kinds of edge — the actors that drive it and the systems it drives — and why the asymmetry between them is the whole point.
0/2 lessons6 questions31 min - 4
Modular Monolith
One deployable unit with real, enforced internal boundaries: what makes a monolith modular rather than merely large, how modules own their data, and how to keep extraction cheap without paying for distribution.
0/3 lessons6 questions43 min - 5
Vertical Slice Architecture
Organise by feature rather than by technical layer, and let each slice be exactly as deep as its problem requires — with an honest account of what you give up.
0/2 lessons6 questions30 min - 6
CQRS
Separating the model you write through from the model you read through: a spectrum of four levels, what each one buys, and why the top of it is rarely justified.
0/2 lessons6 questions32 min - 7
Domain-Driven Design
The strategic half first — bounded contexts, ubiquitous language and context mapping — then the tactical patterns that only pay off once the boundaries are right.
0/2 lessons6 questions34 min