Dependency Inversion Principle in LLD - System Design Guide

Problem Statement

When high-level modules depend directly on low-level modules, changes in low-level details force changes in high-level logic. This tight coupling makes the system fragile and hard to maintain or extend.

Solution

This principle suggests that both high-level and low-level modules should depend on abstractions, not on concrete implementations. By introducing interfaces or abstract classes, the system decouples the high-level logic from low-level details, allowing independent changes and easier testing.

Architecture

High-Level

Module

↓

→Abstraction

This diagram shows both high-level and low-level modules depending on a shared abstraction, which decouples their implementations.

Trade-offs

✓ Pros

→

Improves code maintainability by reducing tight coupling between modules.

→

Enables easier unit testing by allowing mock implementations of abstractions.

→

Supports flexible system extension without modifying existing high-level logic.

✗ Cons

→

Introduces additional abstraction layers, which can increase initial complexity.

→

May require more upfront design effort to define proper interfaces.

→

Can lead to over-engineering if applied unnecessarily in simple systems.

Use when your system has complex business logic that depends on changing low-level details or external services, especially in medium to large codebases with multiple developers.

Avoid when building small, simple applications where abstractions add unnecessary complexity and the codebase is unlikely to change frequently.

Real World Examples

Amazon

Amazon uses dependency inversion to decouple their order processing logic from payment gateway implementations, allowing easy integration of new payment providers without changing core order logic.

Netflix

Netflix applies this principle to separate their streaming service logic from different storage backends, enabling smooth migration and testing.

Uber

Uber uses abstractions to isolate ride matching algorithms from data sources, allowing independent evolution of matching logic and data storage.

Code Example

The before code shows UserService directly creating a MySQLDatabase instance, causing tight coupling. The after code introduces a Database abstraction that UserService depends on, allowing any database implementation to be injected, improving flexibility and testability.

LLD

### Before applying Dependency Inversion Principle (tightly coupled)
class MySQLDatabase:
    def connect(self):
        print("Connecting to MySQL database")

class UserService:
    def __init__(self):
        self.db = MySQLDatabase()  # Direct dependency

    def get_user(self, user_id):
        self.db.connect()
        print(f"Fetching user {user_id}")


### After applying Dependency Inversion Principle (depends on abstraction)
from abc import ABC, abstractmethod

class Database(ABC):
    @abstractmethod
    def connect(self):
        pass

class MySQLDatabase(Database):
    def connect(self):
        print("Connecting to MySQL database")

class UserService:
    def __init__(self, db: Database):
        self.db = db  # Depends on abstraction

    def get_user(self, user_id):
        self.db.connect()
        print(f"Fetching user {user_id}")


# Usage
mysql_db = MySQLDatabase()
service = UserService(mysql_db)
service.get_user(42)

Alternatives

Service Locator

Service Locator centralizes dependency resolution in a registry, whereas Dependency Inversion uses explicit abstractions passed to modules.

Use when: Choose Service Locator when you want to centralize configuration but accept some hidden dependencies.

Factory Pattern

Factory creates objects without exposing instantiation logic, while Dependency Inversion focuses on depending on abstractions rather than concrete classes.

Use when: Choose Factory when object creation logic is complex or varies, but still want to follow Dependency Inversion for dependencies.

Summary

Dependency Inversion Principle reduces tight coupling by making high-level modules depend on abstractions.

It improves maintainability, testability, and flexibility by decoupling implementation details.

Applying it requires thoughtful design of interfaces and careful use of dependency injection.

Practice

1. What is the main goal of the Dependency Inversion Principle in system design?

easy

A. To make high-level modules independent of low-level modules by using abstractions

B. To tightly couple all modules for better performance

C. To avoid using interfaces or abstractions in the system

D. To make low-level modules dependent on high-level modules

Solution

1. Step 1: Understand the principle's purpose

   The Dependency Inversion Principle aims to reduce direct dependencies between high-level and low-level modules.

2. Step 2: Identify the correct approach

   It achieves this by introducing abstractions or interfaces so that high-level modules do not depend on low-level module details.

3. Final Answer:

   To make high-level modules independent of low-level modules by using abstractions -> Option A

4. Quick Check:

   Dependency Inversion = High-level independent [OK]

Hint: Remember: High-level modules depend on abstractions, not details [OK]

Common Mistakes:

• Thinking low-level modules depend on high-level modules
• Ignoring the use of interfaces or abstractions
• Assuming tight coupling improves design

2. Which of the following code snippets correctly demonstrates the Dependency Inversion Principle?

easy

A. class PaymentProcessor { void process(Payment payment) { payment.pay(); } } interface Payment { void pay(); } class CreditCardPayment implements Payment { void pay() { /* pay with card */ } }

B. class PaymentProcessor { void process(CreditCardPayment payment) { payment.pay(); } } class CreditCardPayment { void pay() { /* pay with card */ } }

C. class PaymentProcessor { void process() { CreditCardPayment payment = new CreditCardPayment(); payment.pay(); } } class CreditCardPayment { void pay() { /* pay with card */ } }

D. interface PaymentProcessor { void process(); } class CreditCardPayment implements PaymentProcessor { void process() { /* pay with card */ } }

Solution

1. Step 1: Identify use of abstraction

   class PaymentProcessor { void process(Payment payment) { payment.pay(); } } interface Payment { void pay(); } class CreditCardPayment implements Payment { void pay() { /* pay with card */ } } uses an interface Payment that both PaymentProcessor and CreditCardPayment depend on, following Dependency Inversion.

2. Step 2: Check other options for tight coupling

   Snippets that tightly couple PaymentProcessor to CreditCardPayment by direct reference or instantiation violate DIP. interface PaymentProcessor { void process(); } class CreditCardPayment implements PaymentProcessor { void process() { /* pay with card */ } } reverses roles incorrectly.

3. Final Answer:

   class PaymentProcessor { void process(Payment payment) { payment.pay(); } } interface Payment { void pay(); } class CreditCardPayment implements Payment { void pay() { /* pay with card */ } } -> Option A

4. Quick Check:

   Use interfaces for dependency inversion [OK]

Hint: Look for interfaces or abstractions connecting modules [OK]

Common Mistakes:

• Directly instantiating concrete classes in high-level modules
• Not using interfaces or abstractions
• Confusing interface roles

3. Given the following code, what will be the output?

interface Logger {
  void log(String message);
}

class ConsoleLogger implements Logger {
  public void log(String message) {
    System.out.println("Console: " + message);
  }
}

class Application {
  private Logger logger;
  public Application(Logger logger) {
    this.logger = logger;
  }
  public void run() {
    logger.log("App started");
  }
}

public class Main {
  public static void main(String[] args) {
    Logger logger = new ConsoleLogger();
    Application app = new Application(logger);
    app.run();
  }
}

medium

A. App started

B. Console: App started

C. Compilation error due to missing method

D. Runtime error due to null pointer

Solution

1. Step 1: Trace object creation and method calls

   Main creates a ConsoleLogger and passes it to Application. Calling app.run() calls logger.log("App started").

2. Step 2: Understand the log method behavior

   ConsoleLogger.log prints "Console: " plus the message, so output is "Console: App started".

3. Final Answer:

   Console: App started -> Option B

4. Quick Check:

   Logger prints with prefix "Console:" [OK]

Hint: Follow object creation and method calls step-by-step [OK]

Common Mistakes:

• Ignoring the prefix in print statement
• Assuming direct print of message without prefix
• Confusing interface with implementation

4. Identify the problem in the following design violating the Dependency Inversion Principle:

class FileStorage {
  public void save(String data) {
    // save data to file
  }
}

class DataManager {
  private FileStorage storage = new FileStorage();
  public void saveData(String data) {
    storage.save(data);
  }
}

medium

A. DataManager should create FileStorage inside saveData method

B. FileStorage should not have a save method

C. There is no problem; design follows Dependency Inversion

D. DataManager depends directly on concrete FileStorage instead of an abstraction

Solution

1. Step 1: Analyze dependencies between classes

   DataManager creates and depends directly on concrete FileStorage, causing tight coupling.

2. Step 2: Check for abstraction usage

   There is no interface or abstraction between DataManager and FileStorage, violating Dependency Inversion Principle.

3. Final Answer:

   DataManager depends directly on concrete FileStorage instead of an abstraction -> Option D

4. Quick Check:

   High-level depends on abstraction, not concrete [OK]

Hint: Look for direct use of concrete classes in high-level modules [OK]

Common Mistakes:

• Thinking method placement is the issue
• Ignoring lack of interfaces
• Assuming creating objects inside methods is correct

5. You are designing a notification system that can send messages via Email, SMS, or Push notifications. To follow the Dependency Inversion Principle, which design is best?

hard

A. Each notifier class depends on NotificationManager to get messages.

B. NotificationManager directly creates and calls methods on EmailNotifier, SMSNotifier, and PushNotifier classes.

C. Create an interface Notifier with method send(message), and implement it in EmailNotifier, SMSNotifier, and PushNotifier. The high-level NotificationManager depends on Notifier interface.

D. NotificationManager contains all sending logic inside itself without separate classes.

Solution

1. Step 1: Identify high-level and low-level modules

   NotificationManager is high-level; EmailNotifier, SMSNotifier, PushNotifier are low-level modules.

2. Step 2: Apply Dependency Inversion Principle

   High-level module should depend on abstraction (Notifier interface), not concrete classes. Create an interface Notifier with method send(message), and implement it in EmailNotifier, SMSNotifier, and PushNotifier. The high-level NotificationManager depends on Notifier interface. follows this by using interface and implementations.

3. Final Answer:

   Use Notifier interface implemented by all notifiers; NotificationManager depends on interface -> Option C

4. Quick Check:

   High-level depends on interface, not concrete classes [OK]

Hint: Use interfaces for all notification types to decouple [OK]

Common Mistakes:

• High-level module directly creating concrete classes
• Putting all logic in one class
• Low-level modules depending on high-level modules