Copyright
이 모든 내용은 Pluralsight에 Matthew Renze가 올린 'Clean Architecture: Patterns, Practices, and Principles'라는 강의의 마지막 챕터를 듣고 정리한 것입니다(https://app.pluralsight.com/library/courses/clean-architecture-patterns-practices-principles/table-of-contents). 저작자님께 게시허가도 받았습니다.
Content
2. Domain-centric Architecture
4. Commands and Queries (CQRS)
Last Responsible Moment
Make informed decisions
Deciding too early is a risk
Deciding too late is a risk
Defer decisions until LRM
Evolving the Architecture
Eliminate risk early
Technology may change
Markets may change
Preferences may change
Why Use Evolutionary Architecture?
Pros
Embraces unvertainty
Embraces change
Reduces risk
Cons
Assumes uncertainty
Assumes instability
Still has limitations
Where to Go Next
Books
Patterns of Enterprise Application Architecture
Clean Architecture
Domain-Driven Design
Dependency Injection in .NET
Pluralsite course
Domain-Driven Design Fundamentals
Domain-Driven Design in Practice
Website
Martin Fowler: http://martinfowler.com
Greg Young: http://goodenoughsoftware.net
Udi Dahan: http://udidahan.com
출처
이 모든 내용은 Pluralsight에 Matthew Renze가 올린 'Clean Architecture: Patterns, Practices, and Principles'라는 강의의 마지막 챕터를 듣고 정리한 것입니다(https://app.pluralsight.com/library/courses/clean-architecture-patterns-practices-principles/table-of-contents). 제가 정리한 것보다 더 많은 내용과 Demo를 포함하고 있으며 최종 Summary는 생략하겠습니다. Microsoft 지원을 통해 한달간 무료로 Pluralsight의 강의를 들으실 수도 있습니다.
'Programming > Architecture' 카테고리의 다른 글
| (Modern Software Architecture) The DDD Layered Architecture (0) | 2018.02.14 |
|---|---|
| (Modern Software Architecture) Domain-Driven Design (DDD) (0) | 2018.02.13 |
| (Clean Architecture) Testable Architecture (0) | 2018.02.12 |
| (Clean Architecture) Microservices (0) | 2018.02.12 |
| (Clean Architecture) Functional Organization (0) | 2018.02.11 |
