Timeline for Clean Architecture: Is the Input Boundary necessary?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2019 at 9:40 | comment | added | Laiv | @Engineert you are right. CA pivots very much on DIP | |
| Mar 16, 2019 at 10:36 | comment | added | Laiv | From the book itself, regarding use cases: "Instead they describe the application-specific rules that govern the interaction between the users and the Entities. How data gets in and out of the system is irrelevant to the use cases". Looks like I was right. | |
| Mar 15, 2019 at 11:48 | comment | added | Engineert | If I get wrong please correct me but boundary abstraction is for Controller and/or Presenter. By this abstraction, UI can be testable without depending any other layer and, again I think, this is one of main idea of Clean Architecture. Just avoiding High Level modules dependencies to Low Level is not architecture. It is about DiP. Am I wrong ? | |
| Mar 14, 2019 at 19:01 | comment | added | Laiv | The graph shows relationships: use, extends, implements, etc... The open arrows are "use", the closed are inheritance or implementation. The double lines are architectural boundaries | |
| Mar 14, 2019 at 17:37 | vote | accept | davidh38 | ||
| Mar 15, 2019 at 14:56 | |||||
| Mar 14, 2019 at 17:33 | comment | added | davidh38 | Thank you @Euphoric. Just a follow-up question: can you eloborate how the data flows, because I thought it flows from the controller to the presenter via the use case. Is that correct? | |
| Mar 14, 2019 at 9:19 | comment | added | Euphoric | @Laiv Did you watch Robert C. Martin actually explain the Clean Architecture? youtube.com/watch?v=Nsjsiz2A9mg | |
| Mar 14, 2019 at 9:13 | comment | added | Laiv | Then the output boundary abstraction is also unnecessary for the same reason. Is not it? We could extend both boundaries from the controller layer and use Adapter/Proxy Pattern to gain some decoupling between controller input/output and the interactor input/output. What makes me wonder if these interfaces are just a way to keep implementation details away from the business. In other words simplify the business layer and keep the focus on the logic and not on how things are carried from one layer to another. | |
| Mar 14, 2019 at 6:02 | history | answered | Euphoric | CC BY-SA 4.0 |