Timeline for Where does a Spring Application reside in Hexagonal Architecture
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2023 at 10:16 | comment | added | Claudio Mezzasalma | Yes, this is exactly my point. Since the app needs to sort out dependencies, I think it's not optimal to share this need with the GraphQL adapter. It shouldn't be aware of other dependencies, that's why I think they should be decoupled. | |
| May 18, 2023 at 7:17 | comment | added | Laiv | @ClaudioMezzasalma the app (which is also a layer) is going to be coupled (polluted) by many dependencies because it's the layer where most of the concreteness is solved. The app layer is the layer sorting out the dependency inversion (dependency graph), so it's likely to be aware of many things (concrete adapters, concrete persistence library, concrete framework, ...) | |
| May 18, 2023 at 6:53 | comment | added | Claudio Mezzasalma | Well, more than the package (I should have mentioned I am using Kotlin, so I cannot really achieve package separation here) I was more concerned about the Maven modules, and with it the dependencies of each module. Should I put the main application in the GraphQL adapter module, I would have polluted that module with a lot of other dependencies (other adapters, persistence library). | |
| S May 17, 2023 at 21:05 | review | First answers | |||
| May 18, 2023 at 3:50 | |||||
| S May 17, 2023 at 21:05 | history | answered | Tom | CC BY-SA 4.0 |