Hexagonal, Onion & Clean Architecture

Three similar software architectures explained.
00:00 N-Tier Inversion
01:04 Hexagonal Architecture
01:50 Onion Architecture
02:58 Clean Architecture
Hexagonal Architecture - alistair.cockburn.us/hexagona...
Onion Architecture - jeffreypalermo.com/2008/07/th...
Clean Architecture - blog.cleancoder.com/uncle-bob...

[@ravelinxx]

Finally understood difference between these types of architectures, best video I have found until now.

[@josiahtobas9172]

Great point.

[@larsleo7059]

This was by far the best video about hexagonal architecture i have seen. Good job!

[@creamyhorror]

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.

[@8bitiro]

This has to be the best visual and explanatory video on the topic, thank you!

[@janmeppe]

Honestly one of the best series of boxes I've ever seen :)

[@s1eepr709]

This is the best youtube channel i've ever found that explains things very clearly Thank you!

[@Solovier]

This is the most well explained video of these architectures I always searched for. How this has so low views and likes OMG??

[@zumazumy2257]

The best video ever describing how the architecture evolves .. Thumps up, bro

[@gary6lin]

The best video explains the concept in 5 minutes.

[@nettoaoquadrado]

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!

[@caseyspaulding]

Bravo! So well explained and produced. Thank you.

[@altmystery]

Thank you, excellent video. I have been searching for simple explanation of different layered architectures

[@vitorsantana2795]

What an absolutely fantastic material!! Thanks a lot for this :)

[@Mortlessness]

Good, simple and concise explanation.

[@MohamedEmaish]

Best description i’ve ever seen

[@pedrofaria7322]

That's a wonderful video. Thanks a lot for this.

[@JedaiasRodrigues7]

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.

[@marcelusmeridius]

Sabia que era BR. Caraca, impressionante a explicação sobre as arquiteturas.

[@hakantutkun]

Best explanation ever. Thanks :)

[@joseavilasg]

I can't believe it. Best explanation ever.

[@nadzhafox]

Visual explanation is great!

[@alan-]

This channel rocks

[@almeanawy]

رائع .... حقيقي رائع !

[@farooqmss]

inarguably one of the best explanation on this architecture, music though

[@VidozMusic]

Great video!

[@desdrianton5993]

Best video... Thank you

[@DaemonGenius]

How is there only 6 videos.. @DrawingBoxes.... Your videos are amazing. So simple I love it

[@drawingboxes]

Glad you're enjoying them! More video coming soon - I'm planning to delve into some agile and DevOps topics next

[@alexvgc6170]

best video. Now I understand the difference. :)

[@alibabarahaei2229]

perfect♥

[@ondrejhoos142]

Thank you!

[@khyrian1356]

Life is so much better with sketches ..

[@alexandrusafronovici9734]

THE BEST 👌 ONE

[@tech_excellence]

nice

[@alibabarahaei2229]

best

[@CheDCanal]

I have never faced the "hexagonal architecture" wording in my 11-years career

[@jeanjagnow2524]

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

[@drawingboxes]

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

[@yosiyosiro3866]

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.

[@drawingboxes]

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

[@yosiyosiro3866]

@@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.

[@Pentatonic_Hardcore]

very difficult to understand, still can't get the point

[@abdulgaffarabdulmalik4333]

This seems to come with a Mix of DDD - Domain Services......

[@dvPro-bq9oh2ll1b]

Application is not necessarily enterprise business. "Enterprise business" is buzzword and should not be used in the context of software design.

[@clashclan4739]

Every educational content creators should know background music is totally not required. It is distracting and annoying.

[@alan-]

Get more sleep, you'll concentrate better and not be uptight :)

[@randall.chamberlain]

Every converter on KZbin should phrase their personal preferences as their own and not make a generic statement.

[@usamesavas9848]

Please please please stop putting music in this kind of videos pleaseee