Java Magazine, May/June 2018
Using Domain Driven Design with Java EE How to map DDD artifacts to Java EE code ORACLE COM JAVAMAGAZINE MAY JUNE 2018 50 design patterns Domain driven design as described in the book by Eric Evans aims to construct software models that represent an actual business domain as accurately as possible It especially focuses on the necessity of communicating with domain experts sharing a common ubiquitous domain language refining the understanding of the underlying domain model and gradually refactoring the model Domain driven design DDD describes certain concepts such as bounded contexts aggregates and entities Is it possible to implement the concepts with Java EE or the upcoming Jakarta EE Lets examine these concepts and see how the programming model of modern Java EE enables developers to craft proper domain models starting with some basic definitions Bounded Contexts Bounded contexts enclose the meanings and responsibilities of some part of the domain A specific domain entity contained in a bounded context could be a customer for example The boundaries responsibilities and possible overlaps of bounded contexts are defined in a context map of the system In the model of microservices a bounded context would typically result in a single deployable application Domain Entities Entities represent the business domain entities An important feature of domain entities is that they are identifiable by their nature For entities it matters which entity object is being referred to SEBASTIAN DASCHNER
You must have JavaScript enabled to view digital editions.
