AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: tag blips with related academy trainings

Browse Source
This commit is contained in:
Stefan Rotsch
2024-05-03 11:11:36 +02:00
committed by Stefan Rotsch
parent e5738950cf
commit 291dfd138b
11 changed files with 77 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
radar/2017-03-01/strategic-domain-driven-design.md
View File

@@ -2,17 +2,16 @@
title: "Strategic Domain Driven Design"
ring: adopt
quadrant: methods-and-patterns
tags: [architecture]
tags: [academy training, architecture]
---
Design of distributed applications need to be done wisely. Strategic Domain Driven Design is an approach for modelling large-scale applications and systems and is introduced in the last part of Eric Evans' book _**Domain Driven Design**_.
Designing distributed applications needs to be done wisely. Strategic Domain-Driven Design (DDD) is an approach for modeling large-scale applications and systems, introduced in the last part of Eric Evans' book *Domain-Driven Design*.
Domain driven design is a well-known pattern family and has been established at AOE for quite some time now. Unlike Domain Driven Design, which focuses on the tactical design in an application, strategic domain driven design is an approach that is very helpful for the high-level strategic design of an application and distributed software architecture.
Domain-driven design is a well-known pattern family that has been established at AOE for quite some time now. Unlike Domain-Driven Design, which focuses on the tactical design in an application, strategic Domain-Driven Design is an approach that is very helpful for the high-level strategic design of an application and distributed software architecture.
It is a pattern family focused on using and defining Bounded Context and thinking explicitly of the different relationship patterns and the required "translation" of similar "concepts" between the bounded contexts. It is helpful to argue and find a good strategic architecture in alignment with the requirements, the domain and by considering Conway's Law.
A context map and a common conceptional core help to understand and improve the overall strategic picture. Especially with the [Microservice](/methods-and-patterns/microservices/) approach, it is important to define and connect services following the low coupling - high cohesion principles by idendifying fitting bounded contexts.
It is a pattern family focused on using and defining Bounded Context and thinking explicitly about the different relationship patterns and the required "translation" of similar "concepts" between the bounded contexts. It is helpful to argue and find a good strategic architecture in alignment with the requirements, the domain, and by considering Conway's Law. A context map and a common conceptual core help to understand and improve the overall strategic picture. Especially with the Microservice approach, it is important to define and connect services following the high cohesion - low coupling principles by identifying fitting bounded contexts.
The following chart gives an overview of possible relationships between bounded contexts:
![strategic-domain-driven-design-relationships](/images/strategic-domain-driven-design-relationships.png)
While we have found that this approach is especially useful in designing distributed systems and applications with [microservices](/methods-and-patterns/microservices/), we have also extended this approach to provide guidelines for general enterprise architectures.
While we have found that this approach is especially useful in designing distributed systems and applications with microservices, we have also extended this approach to provide guidelines for general enterprise architectures.