Hexagonal Architecture: What You Need To Know - Simple Explanation

It is important when writing applications to pick the right architecture. Most software developers are familiar with the 3-Tier architecture model already, but few understand Hexagonal Architecture, which I cover in this video. Hexagonal Architecture, which was first coined by Alistair Cockburn in 2005 is a flexible architecture that is great for large applications.

🎓 RECOMMENDED COURSES (Use code FRIENDS10 for 10% off)

📚 RECOMMENDED BOOKS

💻 MY FAVOURITE GEAR

🚀 MY FAVOURITE TOOLS

⏳ TIMESTAMPS
00:00 Introduction
00:11 3 Tier Architecture
00:46 Dependency Injection
01:04 Ports and Adapters Architecture
01:27 The Hexagon
01:34 The Port
02:31 The Adapter
03:05 Input Port and Adapter
03:28 Driving Side and Driven Side
03:39 Why is it called Hexagonal Architecture?
04:30 Domain Driven Design
04:58 STOP, Before you use Hexagonal Architecture
05:03 Pros and Cons of Hexagonal Architecture
05:08 Testability
05:28 Maintainability
05:55 Flexibility
06:20 Complexity in Code
06:36 Running Locally
06:58 Performance
07:24 Should you use Hexagonal Architecture?

You can check out more of my favourite tools on my website:

🔗 MY KEY LINKS

🧑‍💻WHO AM I

‼️ DISCLAIMERS
Some of the links in this description are affiliate links, for which I get a small commission, at no extra cost to you 🙂. I appreciate you supporting my channel so I can continue providing you with free software development content!

#coding #programming #developer

[drondiwe]

hate when I'm being asked like "have you heard of X architecture" and I never heard of it but it turns out that I was using it a lot and I just was asked about its fancy name

[roku_on_it]

I was trying to understand this concept for over 1 week. Things became clear when you quoted the founder saying calling a database is no different than calling/using an external service. I guess we could call it "Adapter Pattern everywhere". I think this subject is being told way more complicated than it actually is, but you kept it fairly simple. Nice explanation!

[tim_abell]

Thanks for including the downsides [00:06:17] - think you nailed it there, basically it's over-engineering unless you have a damn good reason to use it, and frankly I think the terminology introduces more confusion instead of reducing it. Great explanation of what it is and the alleged benefits are.

[MichaelCampbell]

This was great. Of note though, hexagons can still exist in a monolith - the "independently deployed" thing is more a µservice worry than HexArch, although HexArch is common way to do µservices.

[danjelhysenaj]

Hands down this is the simplest explanation that I have ever seen. Excellent Presentation Alex!

[PaulSebastianM]

Great video. For me Clean Architecture and Hexagonal Architecture are just different ways to achieve the same thing: decoupling input and output and increasing feature cohesion. /subbed

[jorisw_]

Simplest and clearest intro I've seen so far. And as with most of these patterns, in the end it's the labeling and metaphors that had obscured most of it or me, whilst the concept itself, once visualized, is simple and clear as day.

[peterbyun]

Thank you for your high-quality content. I love how you explain complex concepts with minimum jargon.

[stormk]

Glad I found this! I'd run across the "no interfaces for repositories" crowd and we'd adopted it at my last gig but in all of my personal work I prefered them for this exact reason. And I especially try to make the interface only have read/write or store/retrieve methods as much as possible to avoid business context dripping down into the repo code. It starts with repo method names that reflect business terminology to me. And for the past 5 years or so I've been bouncing back and forth about the input side as well. Seeing it all in this one pattern has given me some things to consider. Thanks. You have a new subscriber.

[jonathansilva]

Thank you for this simple explanation. I know there might be a lot more details to it, but you beautifully managed to remove the noise so the core concepts (ports and adapters) could shine. Thank you very much.

[saralightbourne]

from the perspective of an active learner, your channel is a treasure. thank you a lot, please don't stop doing what you're doing

[nnutkin]

This is indeed simple explanation. Thank you !

[BRNAMO]

Thanks for the explanation! This video really helps me!

[estevaoyt]

Best explanation of hexagonal architecture! Thank you very much! Keep it up!

[fuadadio]

Thanks for the video. Your explanation is so clear and your animations are so helpful. The video is so clean. I can imagine the amount of work that goes into these videos. Thank you, Alex.

[jhonsen]

Simply brilliant. Clear and concise. 1 Comment and 1 Like from my End.

[Tolmachovtv]

Nice short and clear explanation. Thanks!

[LongNguyen-tco]

Very clear for a newbie as me. Thank you so much

[danclarkeuk]

Great video - one of the clearest explanations I've seen! Nice work! 👍

[khalidelgazzar]

Great video. Watched it a while ago and I keep coming back for a refresher.