The Onion Architecture EXPLAINED | Should we use it?

Whether you are a junior or senior developer, it can be difficult to understand what the onion, hexagonal or clean architectures are. But, most importantly, it’s difficult to figure out how to use them when coding a real application.

In this video, we will start by demystifying the concepts behind the onion architecture and figure out IF and HOW we can use them to build our applications.

🍕 I've got an Italian accent 😅
If you have trouble understanding me, activate the closed captions!
I typed them manually to make sure they are 100% correct!

🌍 Do you want to connect with me? 🌍
Add me on LinkedIn: LinkedIn: marcolenzo
Add me on Twitter: Twitter: marco_lenzo

🤝 Do you need help and want to talk 1 on 1? 🤝
Send me an email!
You find my email, video scripts and more on my website: https://marcolenzo.eu

📕 Books and References 📕
Clean Architecture, Robert C. Martin (Uncle Bob), https://amzn.to/48sLyaT (Amazon Affiliate Link)
Patterns of Enterprise Application Architecture, Martin Fowler, https://amzn.to/3RNXxIY (Amazon Affiliate Link)
The Onion Architecture, Jeffrey Palermo, https://jeffreypalermo.com/2008/07/th...

0:00 Intro
0:29 What is a Layer?
1:49 The Three-Layer architecture explained
3:10 What is the Onion architecture?
5:51 The Core Principles of the Onion architecture
7:32 IoC and DI
8:52 Advantages of the Onion architecture
10:10 Should we use it?
12:41 Clean Architecture

#cleanarchitecture #softwarearchitecture #microservices

• #science_technology
• #onion_architecture
• #clean_architecture
• #hexagonal_architecture
• #domain_driven_design
• #ddd
• #software_architecture
• #patterns_of_enterprise_application_architecture
• #jeffrey_palermo
• #martin_fowler
• #robert_c_martin
• #uncle_bob