How is this architecture different from Uncle Bob's Clean Architecture? #4
-
|
I am curious with all the architectures out there, which to choose for my project? Thank you for your thought. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
As in the hexagonal architecture, business logic is also at the center of clean architecture. Around it are the so-called interface adapters, which connect the core with the user interface, the database, and other external components. The core only knows the interfaces of the adapters but knows nothing about their concrete implementations and the components behind them. In clean architecture, too, all source code dependencies point exclusively in the direction of the core. Where calls point from the inside to the outside, i.e., in the opposite direction to the source code dependency, the dependency inversion principle is applied. The hexagons can be mapped almost one-to-one to the clean architecture rings:
Both architectures are almost identical: the software is divided into layers, and all source code dependencies point from the outer to the inner layers. The application’s core knows no details of the outer layers and is implemented only against their interfaces. This creates a system whose technical details are interchangeable and which is fully testable without them. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much, this is really a thorough answer. |
Beta Was this translation helpful? Give feedback.
-
glad it helps ;) |
Beta Was this translation helpful? Give feedback.
As in the hexagonal architecture, business logic is also at the center of clean architecture. Around it are the so-called interface adapters, which connect the core with the user interface, the database, and other external components. The core only knows the interfaces of the adapters but knows nothing about their concrete implementations and the components behind them.
In clean architecture, too, all source code dependencies point exclusively in the direction of the core. Where calls point from the inside to the outside, i.e., in the opposite direction to the source code dependency, the dependency inversion principle is applied.
The hexagons can be mapped almost one-to-one to the clean a…