Interface Segregation Principle in LLD - System Design Guide

Problem Statement

When a single interface forces clients to depend on methods they do not use, it leads to bloated implementations and fragile code. This causes unnecessary coupling and makes the system harder to maintain and extend.

Solution

This principle solves the problem by splitting large interfaces into smaller, more specific ones. Clients then only implement the interfaces relevant to them, reducing unnecessary dependencies and improving code clarity and flexibility.

Architecture

Client A

→Interface A

↓

Client B

→Interface B

This diagram shows clients depending only on the interfaces they need, each implemented separately, avoiding unnecessary method dependencies.

Trade-offs

✓ Pros

→

Reduces unnecessary dependencies between clients and interfaces.

→

Improves code maintainability by isolating changes to specific interfaces.

→

Enhances flexibility by allowing clients to implement only relevant methods.

→

Facilitates easier testing and mocking of smaller interfaces.

✗ Cons

→

Increases the number of interfaces, which can add complexity to the codebase.

→

Requires careful design to avoid interface explosion with too many tiny interfaces.

→

May require more upfront design effort to identify appropriate interface boundaries.

Use when interfaces have multiple unrelated methods and clients only need subsets of them, especially in medium to large codebases with multiple client types.

Avoid when interfaces are naturally small and cohesive, or in very simple systems where added interface splitting adds unnecessary complexity.

Real World Examples

Amazon

Amazon uses interface segregation in their payment processing system to separate payment authorization, capture, and refund operations, allowing different clients to implement only needed parts.

Netflix

Netflix applies interface segregation in their streaming service APIs to separate playback controls from user preferences, so clients only depend on relevant features.

Uber

Uber uses interface segregation in their driver and rider apps to separate location tracking interfaces from payment interfaces, reducing unnecessary dependencies.

Code Example

The before code forces OldPrinter to implement scan and fax methods it does not support, violating the principle. The after code splits the large interface into smaller ones, so SimplePrinter only implements printing, avoiding unused methods.

LLD

### Before applying Interface Segregation Principle (violating)

class MultiFunctionDevice:
    def print(self, document):
        pass
    def scan(self, document):
        pass
    def fax(self, document):
        pass

class OldPrinter(MultiFunctionDevice):
    def print(self, document):
        print(f"Printing {document}")
    def scan(self, document):
        raise NotImplementedError("Scan not supported")
    def fax(self, document):
        raise NotImplementedError("Fax not supported")


### After applying Interface Segregation Principle (applying)

from abc import ABC, abstractmethod

class Printer(ABC):
    @abstractmethod
    def print(self, document):
        pass

class Scanner(ABC):
    @abstractmethod
    def scan(self, document):
        pass

class Fax(ABC):
    @abstractmethod
    def fax(self, document):
        pass

class SimplePrinter(Printer):
    def print(self, document):
        print(f"Printing {document}")

class MultiFunctionMachine(Printer, Scanner, Fax):
    def print(self, document):
        print(f"Printing {document}")
    def scan(self, document):
        print(f"Scanning {document}")
    def fax(self, document):
        print(f"Faxing {document}")

Alternatives

Single Interface

Uses one large interface with all methods combined, forcing clients to implement unused methods.

Use when: Only when the system is very simple and clients always need all methods.

Abstract Base Class

Uses a base class with default implementations instead of multiple small interfaces.

Use when: When inheritance is preferred and default behavior can be shared.

Summary

Interface Segregation Principle prevents clients from depending on methods they do not use by splitting large interfaces into smaller, specific ones.

This reduces unnecessary coupling, improves maintainability, and increases flexibility in code design.

It is best applied in medium to large systems where clients have diverse needs, but avoided in simple cases to prevent complexity.

Practice

1. What is the main idea behind the Interface Segregation Principle in system design?

easy

A. Interfaces should be as large as possible to cover all features.

B. All classes must implement every method of an interface.

C. Clients should only depend on methods they actually use.

D. Interfaces should be avoided to reduce complexity.

Solution

1. Step 1: Understand the principle's goal

   The Interface Segregation Principle aims to keep interfaces small and focused so clients are not forced to depend on unused methods.

2. Step 2: Match the correct description

   Clients should only depend on methods they actually use. correctly states that clients should only depend on methods they use, which aligns with the principle.

3. Final Answer:

   Clients should only depend on methods they actually use. -> Option C

4. Quick Check:

   Interface Segregation Principle = Clients depend only on used methods [OK]

Hint: Focus on clients using only needed methods [OK]

Common Mistakes:

• Thinking interfaces must be large and cover all features
• Believing all classes must implement every interface method
• Assuming interfaces should be avoided

2. Which of the following interface definitions follows the Interface Segregation Principle?

easy

A. interface Printer { void print(); void scan(); void fax(); }

B. interface Machine { void doEverything(); }

C. interface Device { void operate(); void print(); void scan(); void fax(); }

D. interface Printer { void print(); } interface Scanner { void scan(); }

Solution

1. Step 1: Analyze interface sizes

   interface Printer { void print(); } interface Scanner { void scan(); } splits responsibilities into separate interfaces for printing and scanning, keeping them focused and small.

2. Step 2: Compare with other options

   Options A, B, and C combine multiple unrelated methods into one interface, violating the principle.

3. Final Answer:

   Separate interfaces for each responsibility -> Option D

4. Quick Check:

   Small focused interfaces = interface Printer { void print(); } interface Scanner { void scan(); } [OK]

Hint: Look for interfaces with single focused responsibility [OK]

Common Mistakes:

• Choosing interfaces with many unrelated methods
• Ignoring separation of concerns
• Confusing interface segregation with inheritance

3. Given these interfaces and classes, what will be the output?

interface Printer { void print(); }
interface Scanner { void scan(); }
class MultiFunctionDevice implements Printer, Scanner {
  public void print() { System.out.println("Printing document"); }
  public void scan() { System.out.println("Scanning document"); }
}

MultiFunctionDevice device = new MultiFunctionDevice();
device.print();
device.scan();

medium

A. Printing document\nScanning document

B. Printing document

C. Scanning document

D. Compilation error

Solution

1. Step 1: Understand class implementation

   The class implements both Printer and Scanner interfaces and provides both methods.

2. Step 2: Trace method calls

   Calling device.print() prints "Printing document" and device.scan() prints "Scanning document".

3. Final Answer:

   Printing document\nScanning document -> Option A

4. Quick Check:

   Both methods print messages = Printing document\nScanning document [OK]

Hint: Check which interfaces are implemented and methods called [OK]

Common Mistakes:

• Assuming only one method runs
• Expecting compilation error due to multiple interfaces
• Confusing method outputs

4. Identify the problem in this interface design violating the Interface Segregation Principle:

interface Worker {
  void work();
  void eat();
}

class Robot implements Worker {
  public void work() { System.out.println("Robot working"); }
  public void eat() { throw new UnsupportedOperationException(); }
}

medium

A. Worker interface is too broad, forcing Robot to implement unused methods.

B. Robot should implement eat() properly.

C. Robot class should not implement Worker interface.

D. No problem, this design is correct.

Solution

1. Step 1: Analyze interface methods

   The Worker interface combines work and eat methods, but Robot cannot eat.

2. Step 2: Identify violation

   Robot is forced to implement eat() which it does not support, violating Interface Segregation Principle.

3. Final Answer:

   Worker interface is too broad, forcing Robot to implement unused methods. -> Option A

4. Quick Check:

   Broad interface forcing unused methods = Worker interface is too broad, forcing Robot to implement unused methods. [OK]

Hint: Check if all interface methods apply to all implementers [OK]

Common Mistakes:

• Thinking Robot must implement eat() properly
• Believing no problem exists
• Suggesting Robot should avoid interface

5. You are designing a payment system with interfaces for different payment methods. Which design best follows the Interface Segregation Principle?

hard

A. interface Payment { void payWithCard(); void payWithCash(); void payWithCrypto(); }

B. interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); }

C. interface Payment { void pay(); } class AllPayments implements Payment { void pay() { /* all methods */ } }

D. interface Payment { void payWithCard(); void payWithCash(); } class CryptoPayment implements Payment { void payWithCard() {} void payWithCash() {} }

Solution

1. Step 1: Evaluate interface segregation

   interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); } splits payment methods into separate interfaces, allowing clients to implement only what they need.

2. Step 2: Compare other options

   Options A, B, and D force clients to implement methods they may not use, violating the principle.

3. Final Answer:

   Separate interfaces for each payment method -> Option B

4. Quick Check:

   Separate interfaces = interface CardPayment { void payWithCard(); } interface CashPayment { void payWithCash(); } interface CryptoPayment { void payWithCrypto(); } [OK]

Hint: Split interfaces by payment method for flexibility [OK]

Common Mistakes:

• Combining all payment methods in one interface
• Forcing classes to implement unused methods
• Ignoring interface segregation benefits