Domain-Driven Design: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
An operation offered as an interface that stands along in the model, with no encapsulated state. Also see [[Spring_Dependency_Injection_and_Inversion_of_Control_Container_Concepts#@Service|@Service stereotype]]. | An operation offered as an interface that stands along in the model, with no encapsulated state. Also see [[Spring_Dependency_Injection_and_Inversion_of_Control_Container_Concepts#@Service|@Service stereotype]]. | ||
==Ubiquitous Language== | |||
==Domain Model== | |||
Revision as of 22:11, 23 February 2020
Internal
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.