Layered Architecture: Presentation, Domain, Data
Why separating layers helps — and how layers become a lasagne of pass-through code. Lesson 1 of Level 5: Enterprise Application Architecture.
Level 5 · Enterprise Application Architecture · Lesson 1 of 10
Why separating layers helps — and how layers become a lasagne of pass-through code.
Continue learning
- Composite, Bridge, Mediator, Iterator & Prototype — Previous lesson
- Transaction Script vs Domain Model vs Table Module — Next lesson
- Level 5: Enterprise Application Architecture — Back to the level
All lessons in Enterprise Architecture
- Layered Architecture: Presentation, Domain, Data
- Transaction Script vs Domain Model vs Table Module
- Service Layer: One Front Door for Every Use Case
- Active Record vs Data Mapper (and the Gateways)
- Repository: A Collection-Like Home for Aggregates
- Unit of Work, Identity Map & Lazy Load
- MVC, Front Controller & Friends
- Remote Facade & DTO: Designing Across the Network
- Optimistic vs Pessimistic Offline Locks
- Enterprise Integration Patterns: Messaging Between Systems