LAYERING in ASP.NET Core | Getting Started With ASP.NET Core Series | Dependency Inversion Principle

Video Description

Hello Friends, As applications grow in complexity one way to manage that is to break it up according to various responsibilities or concerns. Following this Separation of concerns principle, helps organize the codebase. It organizes code into different layers, and you might be familiar with this pattern by the name of N-tier, N-Layer, or Layered architecture in general Even though our intentions with Layering is good, I have often seen things go wrong with layering. Any time I make a change, let's say a database table it affects the entire application or at least more than one layer. In this video, let's explore a simple scenario of such an example, why this happens, and what we are doing wrong. I will then show you a guiding principle, the Dependency Inversion Principle, a golden rule that you can follow when separating your code into different layers, folders, or applications. The core design principles of Dependency Inversion and Ownership inversion guide you in managing the dependency flow. It also serves as a guide to organize code into different projects. Additional Watching 📹DEPENDENCY INJECTION in ASP.NET Core - https://youtu.be/YR6HkvNBpX4 📹CONFIGURATION in ASP.NET Core - https://youtu.be/5GlgHV_12-k 📹ASP NET Core Series - https://www.youtube.com/playlist?list=PL59L9XrzUa-nqfCHIKazYMFRKapPNI4sP Come say hi! ✋ 🌍 Blog - https://rahulpnath.com/ ✉ Subscribe to my Newsletter - https://www.rahulpnath.com/subscribe 🐦Twitter - https://twitter.com/rahulpnath 📸Instagram - https://www.instagram.com/rahulpnath/ 🎥 Recording Setup and Workflow - https://www.rahulpnath.com/blog/youtube_setup_and_workflow/ Video Edited by my wife, Parvathy 😍 Make sure to SUBSCRIBE to the channel. THANK YOU for helping me grow this channel !!