Domain-Driven Design: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
* [[Software Architecture#Subjects|Software Architecture]] | * [[Software Architecture#Subjects|Software Architecture]] | ||
* [[Software_Development#Domain-Driven_Design|Software Development]] | * [[Software_Development#Domain-Driven_Design|Software Development]] | ||
=To Read= | |||
* [[DDD]] by Evans | |||
* [https://www.amazon.com/Learning-Domain-Driven-Design-Aligning-Architecture/dp/1098100131/ Learning Domain-Driven Design: Aligning Software Architecture and Business Strategy] by Vlad Khononov | |||
=Overview= | =Overview= | ||
Revision as of 03:43, 1 July 2023
Internal
To Read
- DDD by Evans
- Learning Domain-Driven Design: Aligning Software Architecture and Business Strategy by Vlad Khononov
Overview
An application's domain is the subject area the application addresses. The application's domain defines the ideas and concepts that influence the understanding of the application. The domain is modeled in the application by domain model objects, usually maintained under a "model" subdirectory in the source tree.
Parse DDD.
Concepts
Service
An operation offered as an interface that stands along in the model, with no encapsulated state. Also see @Service stereotype.