Dependency Inversion: What, Why & How? | By Example

preview_player
Показать описание
The Dependency Inversion Principle is one of the key software design principle to manage coupling between software modules. But why is it so important? And how to apply it correctly?

0:00 Intro
0:12 A classic example
1:06 What is DIP?
2:27 Why is it important?
4:04 Applying DIP
5:27 Enhancing DIP
7:16 Appropriate abstractions
10:10 Drawbacks?
10:55 When to use it?
Рекомендации по теме
Комментарии
Автор

Your channel is way underrated. Awesome content and easy to follow along!

CRBarchager
Автор

Great introduction to the idea, this video is criminally underrated.

awesomecraftstudio
Автор

Very amazing content. The DI is not simply DI. You add a context, you explain both for a junior level and an advanced level. Thank you

adriencbl
Автор

Brilliant explanation, easy to wrap your head around. Thank you!

danielokon
Автор

This channel contains some really practical suggestions for how to do Clean Code. Many Thanks! Looking forward to more content. Subcribed!

mehtubbhai
Автор

This was really beautifully explained! I hope your channel will grow more.. Keep it going :)

nicholasziglio
Автор

Finally some basic that I could follow. Using adapter for reusablity of data access in clean architecture. I got some insight, thank you.

yosiyosiro
Автор

Thanks for the content! I have a theoric doubt: in the design using the Adapter pattern, the ModuleB is pertain to Interface Adapter Layer or Infrastructure Layer? I mean, did it become like an external lib for my application?

enggilbertoguimaraes
Автор

So everyone keeps saying about how great it is to use an abstractions for such things as DB, but does it really bring benefits? Do people often change the DB context to something else? Besides something like Logger, which one might change from text to sentry to idk email, everything else is just not happening. The real benefit is in testing/mocking things.

AlexZavalny