Finally a clean and direct presentation of concepts. Love it, though I'll definitely need good implementation examples of onion and clean architectures to understand them.
Nice! Into project having multiple integrations with many apis, this case the integrations modules is adapter? Example: Adapter.Integrations.Service1 Adapter.Integrations.Service2 Adapter.Integrations.Service3
Only if the integrations module has a reference to the application core and those integration services implement 'port' interfaces defined in the core. Not if the application core references the integrations module and directly makes calls to it
I'm happy to be learning English and being able to enjoy incredible content like this! Thank you very much for sharing your knowledge, you have many skills! Congratulations on your genius. For the good of humanity, please continue.
Really good explanation for the hexagonal. Until now i am still confused with the onion layer diagram means. Why the infrastructure layer (data access, email, etc) position should be there? If the depencency is inward, it would not make any sense if data access depends on App Service, then App Service depends on Domain Service, then Domain Service depends on Domain.
Thanks! For the onion architecture, as an example, you could put an IRepository interface in your Domain Services layer. Your App Service layer can use the IRepository to make changes, and your Data Access layer can implement an adapter for IRepository because it has a 'transitive dependency' to that layer going through the App Service layer
@@drawingboxes I see. It is using the same Dependency Inversion explanation in the beginning of video. Onion diagram not intuitive for me. I still need to digging deeper to understand it.
