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.
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.
For onion architecture, shouldn't outer layers also depend only on adjacent layers? But data access seems to depend on IRepository, skipping the whole blue layer at all.
Nope, calls can skip layers. To quote Jeffrey Palermo: "The direction of coupling is toward the center. The big difference is that any outer layer can directly call any inner layer." jeffreypalermo.com/2008/08/the-onion-architecture-part-3/
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
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.
Except that thes resulting graph is not what is written/explained in the book, it's an interpretation with some additions from Drawing Boxes! Especially the Ports inside the Domain(Enterprise Business) layer and 5 instead of 4 layers. It's "their" version of clean architecture. Please call it something different then.
Good spot! In Robert Martin's Clean Architecture diagram, there is one inner circle drawn for 'Enterprise Business Rules', which contains Entities, whereas in our diagram at 4:09 we have kept the circles from Jeffrey Palermo's Onion Architecture diagram, with separate circles for the Domain Model and Domain Services. There is no correct number of layers for Clean Architecture. The main point is that dependencies point inwards and the software is more abstract towards the centre.
Finally understood difference between these types of architectures, best video I have found until now.
Great point.
You just simplified hours and hours of videos in the first minute of your video. Amazing!
This was by far the best video about hexagonal architecture i have seen. Good job!
This has to be the best visual and explanatory video on the topic, thank you!
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.
Honestly one of the best series of boxes I've ever seen :)
This is the most well explained video of these architectures I always searched for. How this has so low views and likes OMG??
This is the best youtube channel i've ever found that explains things very clearly
Thank you!
The best video ever describing how the architecture evolves .. Thumps up, bro
The best video explains the concept in 5 minutes.
Cara, muitíssimo obrigado pelo trabalho. Sou um Dev. Júnior no Brasil e seu vídeo me ajudar pra caramba a entender os conceitos!
Thank you, excellent video. I have been searching for simple explanation of different layered architectures
Bravo! So well explained and produced. Thank you.
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.
Sabia que era BR. Caraca, impressionante a explicação sobre as arquiteturas.
Best video I've found on this topic. Thanks.
What an absolutely fantastic material!! Thanks a lot for this :)
Best description i’ve ever seen
I can't believe it. Best explanation ever.
inarguably one of the best explanation on this architecture, music though
Good, simple and concise explanation.
How is there only 6 videos.. @DrawingBoxes.... Your videos are amazing. So simple I love it
Glad you're enjoying them! More video coming soon - I'm planning to delve into some agile and DevOps topics next
Visual explanation is great!
This channel rocks
Great explanation.
For onion architecture, shouldn't outer layers also depend only on adjacent layers? But data access seems to depend on IRepository, skipping the whole blue layer at all.
Nope, calls can skip layers. To quote Jeffrey Palermo: "The direction of coupling is toward the center. The big difference is that any outer layer can directly call any inner layer." jeffreypalermo.com/2008/08/the-onion-architecture-part-3/
@ thanks 🙏
Life is so much better with sketches ..
Best explanation ever. Thanks :)
perfect♥
That's a wonderful video. Thanks a lot for this.
awesome
رائع .... حقيقي رائع !
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
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.
I have never faced the "hexagonal architecture" wording in my 11-years career
Best video... Thank you
best video. Now I understand the difference. :)
very difficult to understand, still can't get the point
Great video!
Thank you!
THE BEST 👌 ONE
Except that thes resulting graph is not what is written/explained in the book, it's an interpretation with some additions from Drawing Boxes! Especially the Ports inside the Domain(Enterprise Business) layer and 5 instead of 4 layers.
It's "their" version of clean architecture. Please call it something different then.
Good spot! In Robert Martin's Clean Architecture diagram, there is one inner circle drawn for 'Enterprise Business Rules', which contains Entities, whereas in our diagram at 4:09 we have kept the circles from Jeffrey Palermo's Onion Architecture diagram, with separate circles for the Domain Model and Domain Services.
There is no correct number of layers for Clean Architecture. The main point is that dependencies point inwards and the software is more abstract towards the centre.
This seems to come with a Mix of DDD - Domain Services......
nice
best
Application is not necessarily enterprise business.
"Enterprise business" is buzzword and should not be used in the context of software design.
Every educational content creators should know background music is totally not required. It is distracting and annoying.
Get more sleep, you'll concentrate better and not be uptight :)
Every converter on TH-cam should phrase their personal preferences as their own and not make a generic statement.
Yes! There is music. Didn't notice.
Please please please stop putting music in this kind of videos pleaseee