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

adjust text

Browse Source
This commit is contained in:
Daniel Pötzinger
2018-05-09 13:18:45 +02:00
parent 97553cc52e
commit 9955744785
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
radar/2017-10-01/ports-and-adapters.md
View File

@@ -22,13 +22,12 @@ In short here is how we often layer such applications:
* Contains the Applications API and Services, that are developed around the use cases in the application requirements. * Contains the Applications API and Services, that are developed around the use cases in the application requirements.
* This use cases orchestrate the flow of data to and from the domain * This use cases orchestrate the flow of data to and from the domain
* Interfaces: * Interfaces:
* set of adapters that convert data from the format most convenient for the use cases to the format most convenient for some external agency/access * Contains everything required to convert data from the format most convenient for the use cases (e.g. in the application layer) to the format required for some external agency/access
* e.g. (Web) Controllers / DTOs for handling forms etc * e.g. (Web) Controllers / DTOs for handling forms etc
* Infrastructure: * Infrastructure:
* This layer is where all the details go. The Web is a detail. The database is a detail. We keep these things on the outside where they can do little harm. * This layer is where all the (technical) details live. (The database and persitence is a detail, the communication format and mappings with external services is a detail, etc..)
* This is where you can use frameworks and tools such as the RDB Mappers etc. * In this layer you typically have adapters for the secondary ports that have been defined in the layers below. (e.g. an Implementation of a Repository interface from the Domain layer)
* communication details with other external systems (and its DataTransferObjects and Mappers)
This layers belong to every bounded context (modules) inside the application. These layers belong to every bounded context (modules) inside the application.
So if you are searching for a potential timeless architecture for your critical application? Try to implement a potent technology free domain model in the core layer and use ports and adapters to layer your application. So if you are searching for a potential timeless architecture for your critical application? Try to implement a potent technology free domain model in the core layer and use ports and adapters to layer your application.