DDD is Domain-Driven Design , it is a methodology that include ubiquitous language, root entity , value object and aggregations..
DCI: Data, Context, Interactions is a programming paradigm invented by Trygve Reenskaug.
how can I combine with them in a new system?
DDD focuses on three core principles: Focus on the core domain and domain logic . Base complex designs on models of the domain . Constantly collaborate with domain experts , in order to improve the application model and resolve any emerging domain -related issues.
Contents. Domain-Driven Design(DDD) is a collection of principles and patterns that help developers craft elegant object systems. Properly applied it can lead to software abstractions called domain models.
Domain-Driven Design is a concept introduced by a programmer Eric Evans in 2004 in his book Domain-Driven Design: Tackling Complexity in Heart of Software. It is an approach for architecting software design by looking at software in top-down approach.
DDD is used to model the domain entities encapsulating intra-aggregate invariants (validators in constructors). Use cases (from Clean Architecture) are used to orchestrate inter-aggregate business logic in a comprehensible and a targeted way.
This is a subject of on going discussion, and something you'll probably find better answers to at the object-composition Google group where it has been discussed earlier. Also there is an effort to port the canonical DDD sample to DCI at the DCI github page.
Long story overly short though: DCI fits within a Bounded Context, where you'd then have a DCI context per use case.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With