Software Design - What is Dependency Inversion Principle?


Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

You will Learn

  • What is Dependency Inversion Principle?
  • How are Dependency Inversion Principle and Spring Framework related?
  • A few examples of Dependency Inversion Principle in action

Software Design Principles

This is the last article in a series of articles on important Software Design Principles:

What Is Dependency Inversion principle (DIP)?

“Depend Upon Abstractions (interfaces), not Implementations (concrete classes)”

What does this statement mean? Let’s try understanding that with an example:

Let’s look at an example of what this means:


abstract class OutputDevice {
	void copy(String device) {
		Keyboard keyboard = new Keyboard();
		int character;
		while ((character = keyboard.read()) != -1) {
			if (device.equals("Printer")) {
				writeToPrinter(character);
			} else {
				writeToDevice(character);
			}
		}
	}

	private void writeToDevice(int character) {
		// TODO Auto-generated method stub
		
	}

	private void writeToPrinter(int c) {
		// TODO Auto-generated method stub
		
	}
}


What does the copy() method do?

It reads a character from the keyboard, and then decides where this character needs to go. If it’s a printer, write to the printer. Else, send it to the disk.

The problem here is that as the number of OutputDevice types increase, the logic of copy() needs to change every single time.

Let’s look at an alternate implementation:


	public interface Reader {
		public char read();
	}

	public interface Writer {
		public void write(char ch);
	}

	void copy(Reader r, Writer w) {
		int c;

		while((c = r.read()) != EOF) {
			w.write(c);
		}
	}

What we have done here is define two separate interfaces, one to provide the read(), and the other to define the write() methods.

The responsibility of the copy() method is quite clear here: it reads from the Reader interface, and writes whatever it gets to the Writer interface.

copy() now focuses only on the actual operation, and it does so by identifying everything else as its dependencies.

It can now work with any implementation of Reader and Writer interfaces.

DIP and The Spring Framework

DIP is one of the core principles that the Spring Framework enables. Have a look at this example:


	public class BinarySearchImpl {
		public int binarySearch(int[] numbers, int numberToSearchFor) {
			BubbleSortAlgorithm bubbleSortAlgorthm = new BubbleSortAlgorithm();
			int[] sortedNumbers = bubbleSortAlgorithm.sort(numbers);

			//...
		}
	}

BinarySearchImpl directly creates an instance of the BubbleSortAlgorithm. Note that BubbleSortAlgorithm is a dependency of BinarySearchImpl, and as we saw in our previous example, directly accessing it is not a great idea. If you want to switch from a bubble-sort to a quicksort algorithm later, you need to change quite a lot of code inside BinarySearchImpl.

Better Approach for BinarySearchImpl is to make use of an interface - sort algorithm. Here is how our modified code would look like:


	public intrface SortAlgorithm {
		public int[] sort(int[] numbers);
	}

	@Component
	public class BinarySearchImpl {
		@Autowired
		private SortAlgorithm sortAlgorithm;

		public BinarySearchImpl(SortAlgorithm sortAlgorithm) {
			super();
			this.sortAlgorithm = sortAlgorithm;
		}

		public int[] binarySearch(int[] numbers, int numberToSearchFor) {
			int[] sortedNumbers = sortAlgorithm.sort(numbers);
			//...
		}
	}

User of the BinarySearchImpl class, can also pass in a specific implementation of SortAlgorithm, such as a bubble-sort or a quick-sort implementation.

BinarySearchImpl is decoupled from which SortAlgorithm to use.

If you use the Spring framework, you could use the @Autowired annotation with the BinarySearchImpl class, to automatically auto wire an implementation of an available sort algorithm.

By applying the DIP, you make your code more testable. The test code could pass in dependency mocks to properly test the code.

Do check out our video on this:

image info

Summary

Dependency Inversion is about identifying dependencies and externalizing them. You can use a framework like Spring to simplify Dependency Inversion. DIP makes your code more maintainable, reusable and testable.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is creating amazing solutions for you to learn full stack and the cloud - Docker, Kubernetes, AWS, React, Angular etc. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?

Designing REST API - What is Contract First?

Designing Great REST API is important to have great microservices. Contract First approach helps you in designing a great contract before implementing it. However, it does not come easy!