8 Application Architecture
WHAT’S IN THIS CHAPTER?
- Application architecture patterns that protect the integrity of your domain model
- The difference between application and bounded context architectures
- The role and responsibilities of application services
- How to support various application clients
Wrox.com Code Downloads for This Chapter
The wrox.com code downloads for this chapter are found at www.wrox.com/go/domaindrivendesign on the Download Code tab. The code is in the Chapter 8 download and individually named according to the names throughout the chapter.
Domain-Driven Design (DDD) focuses on managing the challenges of building applications with complex domain logic by isolating the business complexities from the technical concerns. Up until now, this book has only looked at techniques to enable teams to model a useful conceptual abstraction of the problem domain. This chapter, however, looks at patterns that enable the domain model to be utilized in the context of an application, taking into consideration persistence, presentation, and other technical requirements.
Developing software while following the principles of DDD does not require you to use any particular application architecture style. But one thing that your architecture must support is the isolation of your domain logic.
Separating the Concerns of Your Application
To avoid turning your codebase into a Big Ball of Mud (BBoM) and thus weakening the integrity and ultimately the ...
Get Patterns, Principles, and Practices of Domain-Driven Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.