Tight coupling vs. Dependency Inversion

Alireza Bonab
2 min readApr 1, 2020

I guess no one more than software developers is fascinated with technology advancements. We are eager with trying new technologies and learning them especially in term of software.

Problem

This is great, you work in a company or founded a startup and as tech person always want to learn new things ( frameworks, databases, UI components and etc. ) but what prevents you to bring or apply new advancements to your software platform, thing that can improve User Experience and Performance.

image from vectorstock

One of the reasons you can not change the platform and stuck with the current frameworks and databases or etc. is Tight Coupling. Yes, Tight Coupling in the heart of your platform prevents you to change it because change means a lot of unwanted consequences and extra work.

Solution

Tight Coupling vs. Dependency Inversion Principle

SOLID is an acronym for 5 important design principles when doing Object Oriented Programming, These principles introduced by Robert C. Martin (Uncle Bob) and then named SOLID.

There is a pattern called Dependency Inversion Principle which is a part of SOLID principles, This pattern in software development says that…

--

--

Alireza Bonab

Entrepreneur in Spirit, Engineer by Training, Adventurist by Nature